bgpreport

Network · data from 2026-11-12

AS40628 OKLAHOMA-OMES

Registry name: OKLAHOMA-OMES - Oklahoma Office of Management & Enterprise Services, US · PeeringDB

13IPv4 routes 92.3% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS40628, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40628, 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.
192.203.164.0/24 No ROA Other IRR onlyRADB 670 100% 69
192.149.244.0/24 Valid Other IRR onlyRADB 670 100% 69
199.27.8.0/21 Valid Other IRR onlyRADB 670 100% 69
199.184.200.0/22 Valid Other IRR onlyRADB 670 100% 69
199.190.128.0/23 Valid Other IRR onlyRADB 670 100% 69
204.61.0.0/21 Valid Other IRR onlyRADB 670 100% 69
204.61.8.0/22 Valid Other IRR onlyRADB 670 100% 69
204.61.12.0/23 Valid Other IRR onlyRADB 670 100% 69
204.62.16.0/21 Valid Other IRR onlyRADB 670 100% 69
204.62.24.0/22 Valid Other IRR onlyRADB 670 100% 69
204.87.64.0/18 Valid Other IRR onlyRADB 670 100% 69
204.144.81.0/24 Valid Other IRR onlyRADB 670 100% 69
205.153.220.0/22 Valid Other IRR onlyRADB 670 100% 69

AS-SET

AS40628'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 14 are in fix.csv.

  • ROA: none1
  • Route object: RIR13
ChangePrefix or setDetailFull-table peers
ROA: none192.203.164.0/24No ROA covers it. Add a ROA for AS40628, maxLength 24.670 of 673
Route object: RIR192.203.164.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR192.149.244.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.27.8.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.184.200.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.190.128.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.61.0.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.61.8.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.61.12.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.62.16.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.62.24.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.87.64.0/18Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.144.81.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR205.153.220.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS40628 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.