bgpreport

Network · data from 2026-11-12

AS51082 ISP-A1-Internet SPUZE LLC

Registry name: ISP-A1-Internet SPUZE LLC, US · not in PeeringDB

11IPv4 routes 90.9% RPKI valid · 72.7% with a route object
5IPv6 routes 80.0% RPKI valid · 80.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
0No ROA 4 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS51082, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS51082, 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.
2a06:a000:102::/48 Invalid: origin None 8 1%low visibility 4
51.194.54.0/24 Invalid: origin None 1 0%low visibility 1
160.236.24.0/24 Valid None 673 100% 67
160.236.25.0/24 Valid None 673 100% 67
148.135.176.0/24 Valid Other IRR onlyRADB 673 100% 67
157.254.12.0/24 Valid Other IRR onlyRADB 673 100% 67
77.83.104.0/24 Valid Other IRR onlyRADB 672 100% 67
23.175.72.0/24 Valid RIR databaseARIN 673 100% 67
64.113.9.0/24 Valid RIR databaseARIN, RADB 673 100% 67
143.203.216.0/22 Valid RIR databaseARIN 671 100% 68
216.224.126.0/24 Valid RIR databaseARIN, RADB 671 100% 68
2602:fd92:141::/48 Valid RIR databaseARIN 634 100% 70
2602:f310:f000::/36 Valid RIR databaseARIN 633 100% 67
2a0c:2e00::/29 Valid RIR databaseRIPE 633 100% 67
173.211.87.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2
2602:f34c:ff00::/40 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS51082 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 22 are in fix.csv.

  • ROA: origin2
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin2a06:a000:102::/48ROAs covering it name AS214420, not AS51082. If AS51082 should announce it, add a ROA for AS51082.8 of 636
Route object: none2a06:a000:102::/48No route object for it. Add a route object with origin AS51082 in the RIR database for the space.8 of 636
ROA: origin51.194.54.0/24ROAs covering it name AS834, not AS51082. If AS51082 should announce it, add a ROA for AS51082.1 of 673
Route object: none51.194.54.0/24No route object for it. Add a route object with origin AS51082 in the RIR database for the space.1 of 673
Route object: none160.236.24.0/24No route object for it. Add a route object with origin AS51082 in the RIR database for the space.673 of 673
Route object: none160.236.25.0/24No route object for it. Add a route object with origin AS51082 in the RIR database for the space.673 of 673
Route object: RIR148.135.176.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.254.12.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR77.83.104.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

23.177.72.0/24ARINValid
2602:fafd:ff0::/44ARINNo ROA
2602:fd92:150::/44ARIN, RADBValid
2602:fd92:600::/40ARINValid
2604:1740::/32ALTDBInvalid: origin
2a11:c940::/32RIPEInvalid: origin
2a11:c941::/32RIPEInvalid: origin
2a11:c942::/32RIPEInvalid: origin
2a11:c943::/32RIPEInvalid: origin
2a11:c944::/32RIPEInvalid: origin
2a11:c945::/32RIPEInvalid: origin
2a11:c946::/32RIPEInvalid: origin
2a11:c947::/32RIPEInvalid: origin

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.