Network · data from 2026-11-12
AS202297 SkylonHost
Registry name: SKYLON Skylon Solutions Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202297, 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.
| 2a0e:fd45:40f6::/48 | No ROA | None | 635 100% |
| 109.248.43.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.8.42.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a0f:5707:ab22::/48 | No ROA | RIR databaseRIPE | 634 100% |
| 2a0c:9a40:8089::/48 | Valid | None | 634 100% |
| 2001:678:aa4::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:ff07::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a14:c380:1a0::/44 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS202297: AS-SKYLON. 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 (AS202297 isn't in the set, or no route object for AS202297 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.
| Name | Database | ASNs | Sets | AS202297 in it | Not covered |
|---|---|---|---|---|---|
| AS-SKYLON | RIPE | 13 | 2 | Yes | 2 |
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: none4
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0e:fd45:40f6::/48 | No ROA covers it. Add a ROA for AS202297, maxLength 48. |
| Route object: none | 2a0e:fd45:40f6::/48 | No route object for it. Add a route object with origin AS202297 in the RIR database for the space. |
| ROA: none | 109.248.43.0/24 | No ROA covers it. Add a ROA for AS202297, maxLength 24. |
| ROA: none | 46.8.42.0/24 | No ROA covers it. Add a ROA for AS202297, maxLength 24. |
| ROA: none | 2a0f:5707:ab22::/48 | No ROA covers it. Add a ROA for AS202297, maxLength 48. |
| Route object: none | 2a0c:9a40:8089::/48 | No route object for it. Add a route object with origin AS202297 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202297 whose prefix no peer sees AS202297 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.139.224.0/22 | RIPE | Valid |
| 91.193.75.0/24 | RIPE | No ROA |
| 2001:678:aa8::/48 | RIPE | Valid |
| 2a04:ff00::/29 | RIPE | No ROA |
| 2a04:ff07:d9::/48 | RIPE | Valid |
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.