Network · data from 2026-11-12
AS393936 TULSA-COUNTY - Metropolitan Tulsa Electronic Network
Registry name: TULSA-COUNTY - Metropolitan Tulsa Electronic Network, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393936, 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.
| 206.202.208.0/24 | No ROA | Nonecovered by 206.202.208.0/23 | 668 99% |
| 206.202.212.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 206.202.213.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 206.202.208.0/23 | No ROA | Other IRR onlyRADB | 668 99% |
| 206.202.210.0/23 | No ROA | Other IRR onlyRADB | 668 99% |
AS-SET
AS393936 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 12 are in fix.csv.
- ROA: none5
- Route object: none1
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 206.202.208.0/24 | No ROA covers it. Add a ROA for AS393936, maxLength 24. |
| Route object: none | 206.202.208.0/24 | No route object for it. A route object for 206.202.208.0/23 with origin AS393936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393936 in the RIR database for the space. |
| ROA: none | 206.202.212.0/24 | No ROA covers it. Add a ROA for AS393936, maxLength 24. |
| Route object: RIR | 206.202.212.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.202.213.0/24 | No ROA covers it. Add a ROA for AS393936, maxLength 24. |
| Route object: RIR | 206.202.213.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.202.208.0/23 | No ROA covers it. Add a ROA for AS393936, maxLength 23. |
| Route object: RIR | 206.202.208.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.202.210.0/23 | No ROA covers it. Add a ROA for AS393936, maxLength 23. |
| Route object: RIR | 206.202.210.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393936 whose prefix no peer sees AS393936 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 206.202.192.0/18 | RADB | No ROA |
| 2620:84:6000::/48 | RADB | 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.