bgpreport

Network · data from 2026-11-12

AS30049 METRO - Metropolitan Transit Authority of Harris County

Registry name: METRO - Metropolitan Transit Authority of Harris County, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30049, 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.225.185.0/24 No ROA Nonecovered by 206.225.184.0/21 671 100% 67
206.225.176.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.177.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.178.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.179.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.180.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.181.0/24 No ROA Other IRR onlyNTTCOM 671 100% 67
206.225.182.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.183.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.184.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.186.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.187.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.188.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.189.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.190.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68
206.225.191.0/24 No ROA Other IRR onlyNTTCOM 671 100% 68

AS-SET

AS30049 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 35 are in fix.csv.

  • ROA: none16
  • Route object: none1
  • Route object: RIR15
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none206.225.185.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: none206.225.185.0/24No route object for it. A route object for 206.225.184.0/21 with origin AS30049 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30049 in the RIR database for the space.671 of 673
ROA: none206.225.176.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.176.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.177.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.177.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.178.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.178.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.179.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.179.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.180.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.180.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.181.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.181.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.182.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.182.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.183.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.183.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.184.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.184.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.186.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.186.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.187.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.187.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.188.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.188.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.189.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.189.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.190.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.190.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none206.225.191.0/24No ROA covers it. Add a ROA for AS30049, maxLength 24.671 of 673
Route object: RIR206.225.191.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS30049 whose prefix no peer sees AS30049 announce. Many are kept on purpose (backup routes, space announced only in some places).

206.225.176.0/20NTTCOMNo ROA
206.225.176.0/22NTTCOMNo ROA
206.225.184.0/21NTTCOMNo 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.