Network · data from 2026-11-12
AS219425 SKYLINE-APP Skyline App LLC
Registry name: SKYLINE-APP Skyline App LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS219425, 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.
| 143.14.104.0/24 | Valid | Nonecovered by 143.14.104.0/22 | 673 100% |
| 143.14.105.0/24 | Valid | Nonecovered by 143.14.104.0/22 | 673 100% |
| 143.14.106.0/24 | Valid | Nonecovered by 143.14.104.0/22 | 673 100% |
| 143.14.107.0/24 | Valid | Nonecovered by 143.14.104.0/22 | 673 100% |
| 2a13:edc0:2::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:5::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:6::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:7::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:8::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:9::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:a::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:b::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:c::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:10::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:11::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:12::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:13::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:14::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:15::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:16::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:17::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:900::/40 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:900::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:910::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:920::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:930::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:edc0:30::/48 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:edc0:3::/48 | Valid | RIR databaseRIPE | 586 92% |
AS-SET
AS219425 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 10 are in fix.csv.
- Route object: none4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 143.14.104.0/24 | No route object for it. A route object for 143.14.104.0/22 with origin AS219425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219425 in the RIR database for the space. |
| Route object: none | 143.14.105.0/24 | No route object for it. A route object for 143.14.104.0/22 with origin AS219425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219425 in the RIR database for the space. |
| Route object: none | 143.14.106.0/24 | No route object for it. A route object for 143.14.104.0/22 with origin AS219425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219425 in the RIR database for the space. |
| Route object: none | 143.14.107.0/24 | No route object for it. A route object for 143.14.104.0/22 with origin AS219425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219425 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS219425 whose prefix no peer sees AS219425 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.40.40.0/21 | RADB, RIPE | Valid |
| 143.14.104.0/22 | RADB, RIPE | Valid |
| 2a13:edc0:4::/48 | RIPE | Valid |
| 2a13:edc0:d::/48 | RIPE | Valid |
| 2a13:edc0:e::/48 | RIPE | Valid |
| 2a13:edc0:f::/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.