Network · data from 2026-11-12
AS200113
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200113, 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.
| 91.226.97.0/24 | Invalid: origin | Other origin only | 7 1%low visibility |
| 85.209.162.0/24 | Invalid: origin | Other origin only | 3 0%low visibility |
| 149.18.96.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
AS-SET
AS200113 isn't in PeeringDB, where networks name their 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 8 are in fix.csv.
- ROA: origin3
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 91.226.97.0/24 | ROAs covering it name AS206007, not AS200113. If AS200113 should announce it, add a ROA for AS200113. |
| Route object: none | 91.226.97.0/24 | Route objects for it name AS206007. Add a route object with origin AS200113 in the RIR database for the space. |
| ROA: origin | 85.209.162.0/24 | ROAs covering it name AS29802, not AS200113. If AS200113 should announce it, add a ROA for AS200113. |
| Route object: none | 85.209.162.0/24 | Route objects for it name AS29802. Add a route object with origin AS200113 in the RIR database for the space. |
| ROA: origin | 149.18.96.0/24 | ROAs covering it name AS213516, not AS200113. If AS200113 should announce it, add a ROA for AS200113. |
| Route object: none | 149.18.96.0/24 | Route objects for it name AS213516. Add a route object with origin AS200113 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS200113 whose prefix no peer sees AS200113 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.177.184.0/24 | AFRINIC | No ROA |
| 2606:f180:11::/48 | ARIN | Invalid: origin |
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.