bgpreport

Network · data from 2026-11-12

AS52939 Minas Turbo Provedor de Internet

Registry name: AS52939 - Minas Turbo Provedor de Internet, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52939, 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:60a4:c000::/44 Valid Nonecovered by 2804:60a4:c000::/34 633 100% 67
2804:60a4:c100::/44 Valid Nonecovered by 2804:60a4:c000::/34 633 100% 67
177.11.87.0/24 Valid Other IRR onlyTC 671 100% 67
177.11.84.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
177.11.84.0/23 Valid Other IRR onlyTC 669 99% 67
177.11.86.0/23 Valid Other IRR onlyTC 669 99% 67
2804:60a4::/33 Valid Other IRR onlyTC 634 100% 67
2804:60a4::/34 Valid Other IRR onlyTC 634 100% 67
2804:60a4:4000::/34 Valid Other IRR onlyTC 634 100% 67
2804:60a4:8000::/33 Valid Other IRR onlyTC 634 100% 67
2804:60a4:8000::/34 Valid Other IRR onlyTC 634 100% 67
2804:60a4:c000::/34 Valid Other IRR onlyTC 634 100% 67
2804:60a4::/32 Valid Other IRR onlyRADB, TC 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS52939: AS52939:AS-MINASTURBO-ALL. 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 (AS52939 isn't in the set, or no route object for AS52939 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 objectsAS52939 in itNot covered
AS52939:AS-MINASTURBO-ALL TC 1311 Yes 0

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

  • Route object: none2
  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: none2804:60a4:c000::/44No route object for it. A route object for 2804:60a4:c000::/34 with origin AS52939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52939 in the RIR database for the space.633 of 636
Route object: none2804:60a4:c100::/44No route object for it. A route object for 2804:60a4:c000::/34 with origin AS52939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52939 in the RIR database for the space.633 of 636
Route object: RIR177.11.87.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.11.84.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.11.84.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.11.86.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:60a4::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:60a4::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:60a4:4000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:60a4:8000::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:60a4:8000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:60a4:c000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:60a4::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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