bgpreport

Network · data from 2026-11-12

AS28591 MCM TELECOM

Registry name: AS28591 - METRO TELECOMUNICACOES S/A, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28591, 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.
177.55.80.0/22 No ROA Nonecovered by 177.55.80.0/21 671 100% 67
177.55.84.0/22 No ROA Nonecovered by 177.55.80.0/21 671 100% 67
200.142.144.0/22 No ROA Nonecovered by 200.142.144.0/20 670 100% 67
200.142.148.0/22 No ROA Nonecovered by 200.142.144.0/20 670 100% 67
200.142.149.0/24 No ROA Nonecovered by 200.142.144.0/20 670 100% 67
200.142.151.0/24 No ROA Nonecovered by 200.142.144.0/20 670 100% 67
200.142.152.0/22 No ROA Nonecovered by 200.142.144.0/20 670 100% 67
2804:178::/33 No ROA Nonecovered by 2804:178::/32 634 100% 67
2804:178:8000::/33 No ROA Nonecovered by 2804:178::/32 634 100% 67
177.55.80.0/21 No ROA Other IRR onlyRADB, TC 667 99% 67
200.142.144.0/20 No ROA Other IRR onlyALTDB, RADB, TC 666 99% 67
2804:178::/32 No ROA Other IRR onlyRADB, TC 631 99% 67

AS-SET

AS28591'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 24 are in fix.csv.

  • ROA: none12
  • Route object: none9
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none177.55.80.0/22No ROA covers it. Add a ROA for AS28591, maxLength 22.671 of 673
Route object: none177.55.80.0/22No route object for it. A route object for 177.55.80.0/21 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.671 of 673
ROA: none177.55.84.0/22No ROA covers it. Add a ROA for AS28591, maxLength 22.671 of 673
Route object: none177.55.84.0/22No route object for it. A route object for 177.55.80.0/21 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.671 of 673
ROA: none200.142.144.0/22No ROA covers it. Add a ROA for AS28591, maxLength 22.670 of 673
Route object: none200.142.144.0/22No route object for it. A route object for 200.142.144.0/20 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.670 of 673
ROA: none200.142.148.0/22No ROA covers it. Add a ROA for AS28591, maxLength 22.670 of 673
Route object: none200.142.148.0/22No route object for it. A route object for 200.142.144.0/20 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.670 of 673
ROA: none200.142.149.0/24No ROA covers it. Add a ROA for AS28591, maxLength 24.670 of 673
Route object: none200.142.149.0/24No route object for it. A route object for 200.142.144.0/20 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.670 of 673
ROA: none200.142.151.0/24No ROA covers it. Add a ROA for AS28591, maxLength 24.670 of 673
Route object: none200.142.151.0/24No route object for it. A route object for 200.142.144.0/20 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.670 of 673
ROA: none200.142.152.0/22No ROA covers it. Add a ROA for AS28591, maxLength 22.670 of 673
Route object: none200.142.152.0/22No route object for it. A route object for 200.142.144.0/20 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.670 of 673
ROA: none2804:178::/33No ROA covers it. Add a ROA for AS28591, maxLength 33.634 of 636
Route object: none2804:178::/33No route object for it. A route object for 2804:178::/32 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.634 of 636
ROA: none2804:178:8000::/33No ROA covers it. Add a ROA for AS28591, maxLength 33.634 of 636
Route object: none2804:178:8000::/33No route object for it. A route object for 2804:178::/32 with origin AS28591 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28591 in the RIR database for the space.634 of 636
ROA: none177.55.80.0/21No ROA covers it. Add a ROA for AS28591, maxLength 21.667 of 673
Route object: RIR177.55.80.0/21Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none200.142.144.0/20No ROA covers it. Add a ROA for AS28591, maxLength 20.666 of 673
Route object: RIR200.142.144.0/20Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:178::/32No ROA covers it. Add a ROA for AS28591, maxLength 32.631 of 636
Route object: RIR2804:178::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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