bgpreport

Network · data from 2026-11-12

AS37580 ELECTRO SHACK

Registry name: ELECTRO SHACK INC. - ELECTRO SHACK INC., LR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37580, 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.
197.215.216.0/22 No ROA RIR databaseAFRINIC, RADB 669 99% 68
197.215.218.0/24 No ROA RIR databaseAFRINIC 669 99% 68
197.215.219.0/24 Valid RIR databaseAFRINIC 671 100% 68
197.215.217.0/24 Valid RIR databaseAFRINIC 669 99% 68
2c0f:4580::/32 Valid RIR databaseAFRINIC 635 100% 69

AS-SET

AS37580'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 3 are in fix.csv.

  • ROA: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none197.215.216.0/22No ROA covers it. Add a ROA for AS37580, maxLength 22.669 of 673
ROA: none197.215.218.0/24No ROA covers it. Add a ROA for AS37580, maxLength 24.669 of 673

Route objects not announced

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

197.215.216.0/24AFRINICValid

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.