bgpreport

Network · data from 2026-11-12

AS271000 MM NET

Registry name: AS271000 - MM NET, BR · PeeringDB

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

Announced routes

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

2804:74bc::/34 Invalid: maxLength Nonecovered by 2804:74bc::/33 37 6%low visibility 23
2804:74bc:4000::/34 Invalid: maxLength Nonecovered by 2804:74bc::/33 37 6%low visibility 23
2804:74bc:8000::/34 Invalid: maxLength Nonecovered by 2804:74bc:8000::/33 37 6%low visibility 23
2804:74bc:c000::/34 Invalid: maxLength Nonecovered by 2804:74bc:8000::/33 37 6%low visibility 23
177.223.128.0/22 Valid Other IRR onlyRADB, TC 665 99% 67
2804:74bc::/32 Valid Other IRR onlyTC 631 99% 67
2804:74bc::/33 Valid Other IRR onlyRADB 631 99% 67
2804:74bc:8000::/33 Valid Other IRR onlyRADB 631 99% 67
177.223.128.0/23 Valid Other IRR onlyTC 0 0%low visibility 1
177.223.130.0/23 Valid Other IRR onlyTC 0 0%low visibility 1

AS-SET

AS271000'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 18 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:74bc::/34ROA 2804:74bc::/32 AS271000 has maxLength 32; ROA 2804:74bc::/33 AS271000 has maxLength 33; the route is a /34. Raise the maxLength, or add a ROA for 2804:74bc::/34.37 of 636
Route object: none2804:74bc::/34No route object for it. A route object for 2804:74bc::/33 with origin AS271000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271000 in the RIR database for the space.37 of 636
ROA: maxLength2804:74bc:4000::/34ROA 2804:74bc::/32 AS271000 has maxLength 32; ROA 2804:74bc::/33 AS271000 has maxLength 33; the route is a /34. Raise the maxLength, or add a ROA for 2804:74bc:4000::/34.37 of 636
Route object: none2804:74bc:4000::/34No route object for it. A route object for 2804:74bc::/33 with origin AS271000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271000 in the RIR database for the space.37 of 636
ROA: maxLength2804:74bc:8000::/34ROA 2804:74bc:8000::/33 AS271000 has maxLength 33; ROA 2804:74bc::/32 AS271000 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2804:74bc:8000::/34.37 of 636
Route object: none2804:74bc:8000::/34No route object for it. A route object for 2804:74bc:8000::/33 with origin AS271000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271000 in the RIR database for the space.37 of 636
ROA: maxLength2804:74bc:c000::/34ROA 2804:74bc:8000::/33 AS271000 has maxLength 33; ROA 2804:74bc::/32 AS271000 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2804:74bc:c000::/34.37 of 636
Route object: none2804:74bc:c000::/34No route object for it. A route object for 2804:74bc:8000::/33 with origin AS271000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271000 in the RIR database for the space.37 of 636
Route object: RIR177.223.128.0/22Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:74bc::/32Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:74bc::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:74bc:8000::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR177.223.128.0/23Route object only in TC. Add it in the RIR database for the space.0 of 673
Route object: RIR177.223.130.0/23Route object only in TC. Add it in the RIR database for the space.0 of 673

Route objects not announced

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

177.223.128.0/24TCValid
177.223.129.0/24RADB, TCValid
177.223.130.0/24RADB, TCValid
177.223.131.0/24RADB, TCValid

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.