AS35745 PROVECTOR-AS Provector Sp. z o.o
π΅π±Org handle: ORG-KPMD2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
18total
17 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)39,184
Announced (BGP)33,280
IPv6 Addresses
Allocated (RIR)7.9Γ10Β²βΈ
Announced (BGP)7.9Γ10Β²βΈ
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
5
Country
π΅π± PLRIR
RIPE NCCStatus
allocated
Allocated
2008-07-14
Routing hygiene
Score 5/100 Β· Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
4
diversity 49/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 18 announced prefixes, updated daily (2026-10-12). How the score works Β· RPKI explained
Announced Prefixes
(BGP)18|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 |
1-10 of 18
1 / 2
Allocated Prefixes
(RIR)30Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.131.160.0/20 | π΅π± PL | RIPENCC | allocated |
| 37.131.164.0/23 | π΅π± PL | RIPE | assigned |
| 37.131.168.0/24 | π΅π± PL | RIPE | assigned |
| 37.131.169.0/24 | π΅π± PL | RIPE | assigned |
| 46.20.48.0/20 | π΅π± PL | RIPENCC | allocated |
| 46.20.48.0/24 | π΅π± PL | RIPE | assigned |
| 46.20.51.0/24 | π΅π± PL | RIPE | assigned |
| 46.20.58.0/24 | π΅π± PL | RIPE | assigned |
| 91.206.108.0/23 | π΅π± PL | RIPENCC | assigned |
| 91.208.50.0/24 | π΅π± PL | RIPENCC | assigned |
1-10 of 30
1 / 3
All 18 announced prefixes of AS35745 β
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS35745 hands its own prefixes to: transit providers, or peers at an exchange.
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS35745 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/35745Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35745" | jq