AS35826 NETSERVERS-AS Netservers Limited
π¬π§Org handle: ORG-NL54-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
13total
11 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)12,288
Announced (BGP)22,528
IPv6 Addresses
Allocated (RIR)7.1Γ10Β²βΉ
Announced (BGP)7.1Γ10Β²βΉ
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
10
Country
π¬π§ GBRIR
RIPE NCCStatus
allocated
Allocated
2005-11-08
Routing hygiene
Score 2/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
6
diversity 79/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 13 announced prefixes, updated daily (2026-10-23). How the score works Β· RPKI explained
Announced Prefixes
(BGP)13|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 |
1-10 of 13
1 / 2
Allocated Prefixes
(RIR)7Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.1.96.0/21 | π¬π§ GB | RIPENCC | allocated |
| 80.248.176.0/20 | π¬π§ GB | RIPENCC | allocated |
| 94.229.128.0/20 | π¬π§ GB | RIPENCC | allocated |
| 185.113.204.0/22 | π¬π§ GB | RIPENCC | allocated |
| 185.229.48.0/22 | π¬π§ GB | RIPENCC | allocated |
| 2a02:700::/32 | π¬π§ GB | RIPENCC | allocated |
| 2a0d:c600::/29 | π¬π§ GB | RIPENCC | allocated |
All 13 announced prefixes of AS35826 β
Upstream Providers(2)
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS205311 | π¬π§Cambridge_Fibre_Networks Cambridge Fibre Networks Ltd. |
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS35826 hands its own prefixes to: transit providers, or peers at an exchange.
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/35826Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35826" | jq