bgpreport

Network · data from 2026-11-12

AS53302 BALTIMORECOUNTYGOVERNMENT - Baltimore County Government

Registry name: BALTIMORECOUNTYGOVERNMENT - Baltimore County Government, US · not in PeeringDB

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

Announced routes

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

207.114.31.0/24 Invalid: origin None 69 10% 41
167.102.138.0/24 No ROA Other IRR onlyRADB 668 99% 67
204.145.181.0/24 No ROA Other IRR onlyRADB 668 99% 67

AS-SET

AS53302 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 6 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: origin207.114.31.0/24ROAs covering it name AS17054, not AS53302. If AS53302 should announce it, add a ROA for AS53302.69 of 673
Route object: none207.114.31.0/24No route object for it. Add a route object with origin AS53302 in the RIR database for the space.69 of 673
ROA: none167.102.138.0/24No ROA covers it. Add a ROA for AS53302, maxLength 24.668 of 673
Route object: RIR167.102.138.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none204.145.181.0/24No ROA covers it. Add a ROA for AS53302, maxLength 24.668 of 673
Route object: RIR204.145.181.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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