bgpreport

Network · data from 2026-11-12

AS55134 SKYNET360 LLC

Registry name: SKYNET360-LLC-7863492000 - SKYNET360 LLC, US · PeeringDB

6IPv4 routes 83.3% 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
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS55134, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55134, 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.
70.42.202.0/23 No ROA Other IRR onlyRADB 223 33% 59
70.34.112.0/20 Valid RIR databaseARIN, RADB 669 99% 67
23.173.72.0/24 Valid RIR databaseARIN, RADB 667 99% 67
69.54.224.0/24 Valid RIR databaseARIN 667 99% 67
69.54.227.0/24 Valid RIR databaseARIN 667 99% 67
172.111.16.0/22 Valid RIR databaseARIN, RADB 667 99% 67
2602:fc67::/36 Valid RIR databaseARIN, RADB 631 99% 67

AS-SET

AS55134'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 4 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none70.42.202.0/23No ROA covers it. Add a ROA for AS55134, maxLength 23.223 of 673
Route object: RIR70.42.202.0/23Route object only in RADB. Add it in the RIR database for the space.223 of 673

Route objects not announced

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

69.54.224.0/19ARINInvalid: origin
69.54.248.0/22ARINInvalid: 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.