bgpreport

Network · data from 2026-11-12

AS52945 E&L Producoes de Software LTDA

Registry name: AS52945 - E&L Producoes de Software Ltda, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% 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
7Route objects not announced registered with origin AS52945, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52945, 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:11e4:200::/41 Valid Nonecovered by 2804:11e4:200::/40 634 100% 67
2804:11e4:280::/41 Valid Nonecovered by 2804:11e4:200::/40 634 100% 67
177.11.212.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 669 99% 67
177.91.192.0/19 Valid Other IRR onlyNTTCOM, RADB, TC 669 99% 67
177.11.212.0/23 Valid Other IRR onlyRADB 665 99% 67
177.11.214.0/23 Valid Other IRR onlyRADB 665 99% 67
2804:11e4::/32 Valid Other IRR onlyRADB, TC 633 100% 67

AS-SET

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

  • Route object: none2
  • Route object: RIR5
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none2804:11e4:200::/41No route object for it. A route object for 2804:11e4:200::/40 with origin AS52945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52945 in the RIR database for the space.634 of 636
Route object: none2804:11e4:280::/41No route object for it. A route object for 2804:11e4:200::/40 with origin AS52945 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52945 in the RIR database for the space.634 of 636
Route object: RIR177.11.212.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.91.192.0/19Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.11.212.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR177.11.214.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:11e4::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

38.210.48.0/22RADBNo ROA
177.11.213.0/24RADBValid
177.91.192.0/20TCValid
177.91.208.0/20RADB, TCValid
2804:11e4::/38TCValid
2804:11e4:200::/40RADBValid
2804:11e4:400::/38TCValid

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.