bgpreport

Network · data from 2026-11-12

AS401075 SKY-SPARK - Skyspark Hosting LLC

Registry name: SKY-SPARK - Skyspark Hosting LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401075, 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.
154.201.94.0/23 Invalid: origin RIR databaseAFRINIC 18 3%low visibility 11
154.201.95.0/24 Invalid: origin RIR databaseAFRINIC 11 2%low visibility 9
154.201.94.0/24 Invalid: origin RIR databaseAFRINIC 4 1%low visibility 2
143.20.38.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
37.202.200.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
2402:1920:fb00::/40 Valid RIR databaseAPNIC 634 100% 67

AS-SET

AS401075 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 11 are in fix.csv.

  • ROA: origin3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin154.201.94.0/23ROAs covering it name AS18013, AS40779, AS55933, AS137899, AS142032, AS401696, AS401701, not AS401075. If AS401075 should announce it, add a ROA for AS401075.18 of 673
ROA: origin154.201.95.0/24ROAs covering it name AS18013, AS40779, AS55933, AS137899, AS142032, AS401696, AS401701, not AS401075. If AS401075 should announce it, add a ROA for AS401075.11 of 673
ROA: origin154.201.94.0/24ROAs covering it name AS18013, AS40779, AS55933, AS137899, AS142032, AS401696, AS401701, not AS401075. If AS401075 should announce it, add a ROA for AS401075.4 of 673

Route objects not announced

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

23.177.120.0/24ARINValid
94.241.160.0/23RADB, RIPEValid
2402:1920:f800::/38APNICValid
2402:1920:f800::/39APNICValid
2402:1920:f800::/40APNICValid
2402:1920:f900::/40APNICValid
2402:1920:fa00::/39APNICValid
2402:1920:fa00::/40APNICValid

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.