Network · data from 2026-11-12
AS35071 Xoom
Registry name: UK-XOOM-SYSTEMS-AS Xoom Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35071, 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.
| 31.22.40.0/21 | No ROA | None | 671 100% |
| 185.147.208.0/22 | No ROA | None | 671 100% |
| 185.147.209.0/24 | No ROA | Nonecovered by 185.147.208.0/23 | 671 100% |
| 31.22.44.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.95.76.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.95.76.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.95.77.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 31.22.40.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 185.95.78.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 185.95.79.0/24 | No ROA | RIR databaseRIPE | 411 61% |
| 185.147.208.0/23 | No ROA | RIR databaseRIPE | 3 0%low visibility |
| 185.147.210.0/23 | No ROA | RIR databaseRIPE | 3 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS35071: AS-SET-XOOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS35071 isn't in the set, or no route object for AS35071 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS35071 in it | Not covered |
|---|---|---|---|---|---|
| AS-SET-XOOM | RIPE | 5 | 2 | Yes | 2 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 17 are in fix.csv.
- ROA: none12
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 31.22.40.0/21 | No ROA covers it. Add a ROA for AS35071, maxLength 21. |
| Route object: none | 31.22.40.0/21 | No route object for it. Add a route object with origin AS35071 in the RIR database for the space. |
| ROA: none | 185.147.208.0/22 | No ROA covers it. Add a ROA for AS35071, maxLength 22. |
| Route object: none | 185.147.208.0/22 | No route object for it. Add a route object with origin AS35071 in the RIR database for the space. |
| ROA: none | 185.147.209.0/24 | No ROA covers it. Add a ROA for AS35071, maxLength 24. |
| Route object: none | 185.147.209.0/24 | No route object for it. A route object for 185.147.208.0/23 with origin AS35071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35071 in the RIR database for the space. |
| ROA: none | 31.22.44.0/22 | No ROA covers it. Add a ROA for AS35071, maxLength 22. |
| ROA: none | 185.95.76.0/22 | No ROA covers it. Add a ROA for AS35071, maxLength 22. |
| ROA: none | 185.95.76.0/24 | No ROA covers it. Add a ROA for AS35071, maxLength 24. |
| ROA: none | 185.95.77.0/24 | No ROA covers it. Add a ROA for AS35071, maxLength 24. |
| ROA: none | 31.22.40.0/22 | No ROA covers it. Add a ROA for AS35071, maxLength 22. |
| ROA: none | 185.95.78.0/24 | No ROA covers it. Add a ROA for AS35071, maxLength 24. |
| ROA: none | 185.95.79.0/24 | No ROA covers it. Add a ROA for AS35071, maxLength 24. |
| ROA: none | 185.147.208.0/23 | No ROA covers it. Add a ROA for AS35071, maxLength 23. |
| ROA: none | 185.147.210.0/23 | No ROA covers it. Add a ROA for AS35071, maxLength 23. |
Route objects not announced
Route objects with origin AS35071 whose prefix no peer sees AS35071 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.10.209.0/24 | RIPE | Invalid: origin |
| 2a04:fe80::/29 | RIPE | No ROA |
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.