bgpreport

Network · data from 2026-11-12

AS52958 AS52958 - Empr.Tec.Inform.Comun. Mun.SP-PRODAM-SP S/A

Registry name: AS52958 - Empr.Tec.Inform.Comun. Mun.SP-PRODAM-SP S/A, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52958, 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.
177.22.128.0/20 No ROA None 671 100% 67
177.22.144.0/20 No ROA None 671 100% 67
177.22.136.0/21 No ROA None 670 100% 67
177.22.144.0/21 No ROA None 670 100% 67
177.22.152.0/21 No ROA None 670 100% 67
177.22.128.0/21 No ROA None 669 99% 67
2801:94::/48 No ROA None 636 100% 67
2801:94::/32 No ROA None 634 100% 67

AS-SET

AS52958 isn't in PeeringDB, where networks name their 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: none177.22.128.0/20No ROA covers it. Add a ROA for AS52958, maxLength 20.671 of 673
Route object: none177.22.128.0/20No route object for it. Add a route object with origin AS52958 in the RIR database for the space.671 of 673
ROA: none177.22.144.0/20No ROA covers it. Add a ROA for AS52958, maxLength 20.671 of 673
Route object: none177.22.144.0/20No route object for it. Add a route object with origin AS52958 in the RIR database for the space.671 of 673
ROA: none177.22.136.0/21No ROA covers it. Add a ROA for AS52958, maxLength 21.670 of 673
Route object: none177.22.136.0/21No route object for it. Add a route object with origin AS52958 in the RIR database for the space.670 of 673
ROA: none177.22.144.0/21No ROA covers it. Add a ROA for AS52958, maxLength 21.670 of 673
Route object: none177.22.144.0/21No route object for it. Add a route object with origin AS52958 in the RIR database for the space.670 of 673
ROA: none177.22.152.0/21No ROA covers it. Add a ROA for AS52958, maxLength 21.670 of 673
Route object: none177.22.152.0/21No route object for it. Add a route object with origin AS52958 in the RIR database for the space.670 of 673
ROA: none177.22.128.0/21No ROA covers it. Add a ROA for AS52958, maxLength 21.669 of 673
Route object: none177.22.128.0/21No route object for it. Add a route object with origin AS52958 in the RIR database for the space.669 of 673
ROA: none2801:94::/48No ROA covers it. Add a ROA for AS52958, maxLength 48.636 of 636
Route object: none2801:94::/48No route object for it. Add a route object with origin AS52958 in the RIR database for the space.636 of 636
ROA: none2801:94::/32No ROA covers it. Add a ROA for AS52958, maxLength 32.634 of 636
Route object: none2801:94::/32No route object for it. Add a route object with origin AS52958 in the RIR database for the space.634 of 636

Route objects not announced

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