bgpreport

Network · data from 2026-11-12

AS15196 MDDOT - Maryland Department of Transportation

Registry name: MDDOT - Maryland Department of Transportation, US · not in PeeringDB

7IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
7No 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 AS15196, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS15196, 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.

170.93.0.0/16 No ROA Other IRR onlyRADB 668 99% 68
170.93.142.0/23 No ROA Other IRR onlyRADB 668 99% 68
170.93.140.0/23 No ROA Other IRR onlyRADB 666 99% 68
170.93.144.0/24 No ROA Other IRR onlyRADB 666 99% 68
170.93.145.0/24 No ROA Other IRR onlyRADB 666 99% 68
170.93.226.0/24 No ROA Other IRR onlyRADB 666 99% 68
170.93.227.0/24 No ROA Other IRR onlyRADB 666 99% 68

AS-SET

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

  • ROA: none7
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none170.93.0.0/16No ROA covers it. Add a ROA for AS15196, maxLength 16.668 of 673
Route object: RIR170.93.0.0/16Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none170.93.142.0/23No ROA covers it. Add a ROA for AS15196, maxLength 23.668 of 673
Route object: RIR170.93.142.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none170.93.140.0/23No ROA covers it. Add a ROA for AS15196, maxLength 23.666 of 673
Route object: RIR170.93.140.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none170.93.144.0/24No ROA covers it. Add a ROA for AS15196, maxLength 24.666 of 673
Route object: RIR170.93.144.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none170.93.145.0/24No ROA covers it. Add a ROA for AS15196, maxLength 24.666 of 673
Route object: RIR170.93.145.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none170.93.226.0/24No ROA covers it. Add a ROA for AS15196, maxLength 24.666 of 673
Route object: RIR170.93.226.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none170.93.227.0/24No ROA covers it. Add a ROA for AS15196, maxLength 24.666 of 673
Route object: RIR170.93.227.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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