bgpreport

Network · data from 2026-11-12

AS53274 Skyrunner

Registry name: SKYRUNNER-INC - Skyrunner, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53274, 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.

44.74.5.0/24 No ROA None 26 4%low visibility 17
199.168.207.0/24 Valid RIR databaseARIN 673 100% 67
204.48.56.0/23 Valid RIR databaseARIN 673 100% 67
204.48.56.0/24 Valid RIR databaseARIN 673 100% 67
204.48.57.0/24 Valid RIR databaseARIN 673 100% 67
204.48.58.0/23 Valid RIR databaseARIN 673 100% 67
204.48.58.0/24 Valid RIR databaseARIN 673 100% 67
204.48.59.0/24 Valid RIR databaseARIN 673 100% 67
162.255.168.0/22 Valid RIR databaseARIN 671 100% 68
162.255.168.0/23 Valid RIR databaseARIN 671 100% 68
162.255.168.0/24 Valid RIR databaseARIN 671 100% 68
162.255.169.0/24 Valid RIR databaseARIN 671 100% 68
162.255.170.0/23 Valid RIR databaseARIN 671 100% 68
162.255.170.0/24 Valid RIR databaseARIN 671 100% 68
162.255.171.0/24 Valid RIR databaseARIN 671 100% 68
199.168.200.0/22 Valid RIR databaseARIN 671 100% 68
199.168.200.0/23 Valid RIR databaseARIN 671 100% 68
199.168.200.0/24 Valid RIR databaseARIN 671 100% 68
199.168.201.0/24 Valid RIR databaseARIN 671 100% 68
199.168.202.0/23 Valid RIR databaseARIN 671 100% 68
199.168.202.0/24 Valid RIR databaseARIN 671 100% 68
199.168.203.0/24 Valid RIR databaseARIN 671 100% 68
199.168.204.0/24 Valid RIR databaseARIN 671 100% 67
199.168.205.0/24 Valid RIR databaseARIN 671 100% 68
199.168.206.0/24 Valid RIR databaseARIN 671 100% 68
2602:ff8f:fff::/48 Valid RIR databaseARIN 636 100% 68
2602:ff8f::/40 Valid RIR databaseARIN 635 100% 69
2602:ff8f::/41 Valid RIR databaseARIN 635 100% 69
2602:ff8f:80::/41 Valid RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS53274: AS-53274. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS53274 isn't in the set, or no route object for AS53274 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS53274 in itNot covered
AS-53274 ARIN 3145 Yes 1

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

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none44.74.5.0/24No ROA covers it. Add a ROA for AS53274, maxLength 24.26 of 673
Route object: none44.74.5.0/24No route object for it. Add a route object with origin AS53274 in the RIR database for the space.26 of 673

Route objects not announced

Every route object with origin AS53274 is announced.

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.