bgpreport

Network · data from 2026-11-12

AS52986 Vupt Provedora de Internet

Registry name: AS52986 - Vupt Provedora de Internet Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52986, 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:9844::/32 Valid None 632 99% 67
2804:9844::/33 Valid None 632 99% 67
2804:9844::/34 Valid None 632 99% 67
2804:9844:4000::/34 Valid None 632 99% 67
2804:9844:8000::/33 Valid None 632 99% 67
2804:9844:8000::/34 Valid None 632 99% 67
2804:9844:c000::/34 Valid None 632 99% 67
177.52.208.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
177.52.209.0/24 Valid Other IRR onlyTC 671 100% 66
177.52.208.0/24 Valid Other IRR onlyTC 670 100% 66
177.52.210.0/24 Valid Other IRR onlyTC 670 100% 66
177.52.211.0/24 Valid Other IRR onlyTC 670 100% 66

AS-SET

AS52986'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 12 are in fix.csv.

  • Route object: none7
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
Route object: none2804:9844::/32No route object for it. Add a route object with origin AS52986 in the RIR database for the space.632 of 636
Route object: none2804:9844::/33No route object for it. Add a route object with origin AS52986 in the RIR database for the space.632 of 636
Route object: none2804:9844::/34No route object for it. Add a route object with origin AS52986 in the RIR database for the space.632 of 636
Route object: none2804:9844:4000::/34No route object for it. Add a route object with origin AS52986 in the RIR database for the space.632 of 636
Route object: none2804:9844:8000::/33No route object for it. Add a route object with origin AS52986 in the RIR database for the space.632 of 636
Route object: none2804:9844:8000::/34No route object for it. Add a route object with origin AS52986 in the RIR database for the space.632 of 636
Route object: none2804:9844:c000::/34No route object for it. Add a route object with origin AS52986 in the RIR database for the space.632 of 636
Route object: RIR177.52.208.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.52.209.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.52.208.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.52.210.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.52.211.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673

Route objects not announced

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