bgpreport

Network · data from 2026-11-12

AS54904 EVOLVE-COMMUNICATIONS - Evolve Communications Inc

Registry name: EVOLVE-COMMUNICATIONS - Evolve Communications Inc, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54904, 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.
2605:3b40::/32 No ROA Other IRR onlyRADB 605 95% 67

AS-SET

AS54904 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.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2605:3b40::/32No ROA covers it. Add a ROA for AS54904, maxLength 32.605 of 636
Route object: RIR2605:3b40::/32Route object only in RADB. Add it in the RIR database for the space.605 of 636

Route objects not announced

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

147.160.40.0/23RADBNo ROA
147.160.40.0/24RADBNo ROA
147.160.41.0/24RADBNo ROA
147.160.42.0/23RADBNo ROA
147.160.42.0/24RADBNo ROA
147.160.43.0/24RADBNo 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.