bgpreport

Network · data from 2026-11-12

AS267076 REDE MINEIRA DE TELECOMUNICAÇÕES LTDA

Registry name: AS267076 - REDE MINEIRA DE TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267076, 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.
45.228.204.0/24 Invalid: maxLength Nonecovered by 45.228.204.0/22 33 5%low visibility 16
45.228.204.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
2804:47c8::/32 Valid Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS267076: AS-REDEMINEIRA. 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 (AS267076 isn't in the set, or no route object for AS267076 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 objectsAS267076 in itNot covered
AS-REDEMINEIRA 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 5 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR2
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.228.204.0/24ROA 45.228.204.0/22 AS267076 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 45.228.204.0/24.33 of 673
Route object: none45.228.204.0/24No route object for it. A route object for 45.228.204.0/22 with origin AS267076 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267076 in the RIR database for the space.33 of 673
Route object: RIR45.228.204.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:47c8::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
AS-SET: not foundAS-REDEMINEIRAPeeringDB names AS-REDEMINEIRA; no IRR database read has it.

Route objects not announced

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