bgpreport

Network · data from 2026-11-12

AS61801 AS61801 - Eletropaulo Metropolitana Eletric. de S. Paulo S/A

Registry name: AS61801 - Eletropaulo Metropolitana Eletric. de S. Paulo S/A, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61801, 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.
189.108.130.8/30 No ROA None 2 0%low visibility 2
201.131.209.0/24 No ROA Other IRR onlyRADB 671 100% 67
201.131.208.0/22 No ROA Other IRR onlyRADB 670 100% 66
201.131.208.0/24 No ROA Other IRR onlyRADB 670 100% 66
201.131.210.0/24 No ROA Other IRR onlyRADB 670 100% 67
201.131.211.0/24 No ROA Other IRR onlyRADB 670 100% 66

AS-SET

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

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none189.108.130.8/30No ROA covers it. Add a ROA for AS61801, maxLength 30.2 of 673
Route object: none189.108.130.8/30No route object for it. Add a route object with origin AS61801 in the RIR database for the space.2 of 673
ROA: none201.131.209.0/24No ROA covers it. Add a ROA for AS61801, maxLength 24.671 of 673
Route object: RIR201.131.209.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none201.131.208.0/22No ROA covers it. Add a ROA for AS61801, maxLength 22.670 of 673
Route object: RIR201.131.208.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none201.131.208.0/24No ROA covers it. Add a ROA for AS61801, maxLength 24.670 of 673
Route object: RIR201.131.208.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none201.131.210.0/24No ROA covers it. Add a ROA for AS61801, maxLength 24.670 of 673
Route object: RIR201.131.210.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none201.131.211.0/24No ROA covers it. Add a ROA for AS61801, maxLength 24.670 of 673
Route object: RIR201.131.211.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

201.131.208.0/23RADBNo ROA
2801:80:b10::/48RADBNo ROA

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.