bgpreport

Network · data from 2026-11-12

AS267158 MG NET TELECOMUNICACOES LTDA ­ ME

Registry name: AS267158 - MG NET TELECOMUNICACOES LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267158, 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:3e88::/32 Invalid: origin Other origin only 19 3%low visibility 8
45.230.68.0/22 Valid Other IRR onlyTC 671 100% 66
45.230.69.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
45.230.68.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
45.230.70.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
2804:4900::/32 Valid Other IRR onlyRADB, TC 633 100% 67
2804:4900::/34 Valid Other IRR onlyRADB 633 100% 67
2804:4900:8000::/33 Valid Other IRR onlyRADB 633 100% 67
2804:4900:8000::/34 Valid Other IRR onlyRADB 633 100% 67
2804:4900:c000::/34 Valid Other IRR onlyRADB 633 100% 67
45.230.71.0/24 Valid Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS267158: AS267158:AS-MG. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS267158 isn't in the set, or no route object for AS267158 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS267158 in itNot covered
AS267158:AS-MG In no IRR database read today.

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

  • ROA: origin1
  • Route object: none1
  • Route object: RIR10
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2804:3e88::/32ROAs covering it name AS266603, not AS267158. If AS267158 should announce it, add a ROA for AS267158.19 of 636
Route object: none2804:3e88::/32Route objects for it name AS266603. Add a route object with origin AS267158 in the RIR database for the space.19 of 636
Route object: RIR45.230.68.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.230.69.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.230.68.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.230.70.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:4900::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4900::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4900:8000::/33Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4900:8000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4900:c000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR45.230.71.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
AS-SET: not foundAS267158:AS-MGPeeringDB names AS267158:AS-MG; no IRR database read has it.

Route objects not announced

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

45.230.68.0/23RADB, TCValid
45.230.70.0/23TCValid

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.