Network · data from 2026-11-12
AS204139 NEXTGLOBALSERVICES NEXT GLOBAL SERVICES L.P.
Registry name: NEXTGLOBALSERVICES NEXT GLOBAL SERVICES L.P., GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204139, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2.59.200.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 88.218.148.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.122.124.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.122.126.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.123.240.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.123.242.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.123.248.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.123.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.128.134.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.128.176.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.128.178.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.129.20.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.129.22.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 5.183.60.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 147.78.226.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 185.110.0.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 185.110.2.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 185.122.128.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 185.127.46.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 185.132.8.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 185.132.10.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 185.127.44.0/23 | Valid | RIR databaseRIPE | 665 99% |
AS-SET
AS204139 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS204139 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.