bgpreport

Network · data from 2026-11-12

AS61813 AS61813 - EDGE4M CONSULTORIA EM INFRAESTRUTURA LTDA.

Registry name: AS61813 - EDGE4M CONSULTORIA EM INFRAESTRUTURA LTDA., BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61813, 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.
201.159.157.0/24 Valid Nonecovered by 201.159.156.0/22 671 100% 66
138.122.196.0/24 Valid Nonecovered by 138.122.196.0/22 667 99% 67
201.159.156.0/24 Valid Nonecovered by 201.159.156.0/22 667 99% 67
201.159.158.0/24 Valid Nonecovered by 201.159.156.0/22 667 99% 67
2804:19b4:1::/48 Valid Nonecovered by 2804:19b4::/32 635 100% 67
138.122.196.0/22 Valid Other IRR onlyRADB 667 99% 67
2804:19b4::/32 Valid Other IRR onlyRADB 343 54% 62

AS-SET

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

  • Route object: none5
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none201.159.157.0/24No route object for it. A route object for 201.159.156.0/22 with origin AS61813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61813 in the RIR database for the space.671 of 673
Route object: none138.122.196.0/24No route object for it. A route object for 138.122.196.0/22 with origin AS61813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61813 in the RIR database for the space.667 of 673
Route object: none201.159.156.0/24No route object for it. A route object for 201.159.156.0/22 with origin AS61813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61813 in the RIR database for the space.667 of 673
Route object: none201.159.158.0/24No route object for it. A route object for 201.159.156.0/22 with origin AS61813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61813 in the RIR database for the space.667 of 673
Route object: none2804:19b4:1::/48No route object for it. A route object for 2804:19b4::/32 with origin AS61813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61813 in the RIR database for the space.635 of 636
Route object: RIR138.122.196.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:19b4::/32Route object only in RADB. Add it in the RIR database for the space.343 of 636

Route objects not announced

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

201.159.156.0/22RADBValid

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.