24IPv4 routes
100.0% RPKI valid · 16.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
20 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS16732, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS16732, 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.
| 200.59.33.0/24 | Valid | None | 669 99% |
| 200.59.34.0/24 | Valid | None | 669 99% |
| 200.59.36.0/24 | Valid | None | 669 99% |
| 200.59.37.0/24 | Valid | None | 669 99% |
| 200.59.38.0/24 | Valid | None | 669 99% |
| 200.59.40.0/24 | Valid | None | 669 99% |
| 200.59.42.0/24 | Valid | None | 669 99% |
| 200.59.43.0/24 | Valid | None | 669 99% |
| 200.59.44.0/24 | Valid | None | 669 99% |
| 200.59.45.0/24 | Valid | None | 669 99% |
| 200.59.46.0/24 | Valid | None | 669 99% |
| 200.59.47.0/24 | Valid | None | 669 99% |
| 200.59.50.0/24 | Valid | None | 669 99% |
| 200.59.51.0/24 | Valid | None | 669 99% |
| 200.59.55.0/24 | Valid | None | 669 99% |
| 200.59.58.0/24 | Valid | None | 669 99% |
| 200.59.207.0/24 | Valid | None | 669 99% |
| 200.59.52.0/24 | Valid | None | 668 99% |
| 200.59.53.0/24 | Valid | None | 668 99% |
| 200.59.39.0/24 | Valid | None | 667 99% |
| 200.59.32.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 200.59.35.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 200.59.41.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 200.59.200.0/22 | Valid | Other IRR onlyRADB | 669 99% |
AS-SET
AS16732's PeeringDB record names no AS-SET.
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 24 are in fix.csv.
- Route object: none20
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.59.33.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.34.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.36.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.37.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.38.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.40.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.42.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.43.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.44.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.45.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.46.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.47.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.50.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.51.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.55.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.58.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.207.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.52.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.53.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: none | 200.59.39.0/24 | No route object for it. Add a route object with origin AS16732 in the RIR database for the space. |
| Route object: RIR | 200.59.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.59.35.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.59.41.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.59.200.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS16732 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.