bgpreport

Network · data from 2026-11-12

AS202520 SkyPass Solutions

Registry name: SKYPASS-AS SkyPass Solutions Sp. z o.o., PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202520, 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.
83.168.110.0/24 No ROA RIR databaseRIPE 673 100% 66
2001:678:8e8::/48 No ROA RIR databaseRIPE 635 100% 67
2001:67c:b58::/48 No ROA RIR databaseRIPE 635 100% 67
83.168.68.0/23 Valid RIR databaseRIPE 673 100% 66
83.168.94.0/24 Valid RIR databaseRIPE 673 100% 66
83.168.95.0/24 Valid RIR databaseRIPE 673 100% 66
83.168.105.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
83.168.107.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
96.62.191.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
146.103.49.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
147.79.24.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
147.79.62.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
83.168.106.0/24 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS202520: AS202520:AS-CLIENTS. 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 (AS202520 isn't in the set, or no route object for AS202520 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 objectsAS202520 in itNot covered
AS202520:AS-CLIENTS RIPElists itself further down11 member sets in no database: AS-24IT, AS-CFLD, AS-EURON, AS-INVITEL-UA, AS-LINXTELECOM-PL … 1,69923819,287 Yes 0

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

  • ROA: none3
  • AS-SET: missing member11
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none83.168.110.0/24No ROA covers it. Add a ROA for AS202520, maxLength 24.673 of 673
ROA: none2001:678:8e8::/48No ROA covers it. Add a ROA for AS202520, maxLength 48.635 of 636
ROA: none2001:67c:b58::/48No ROA covers it. Add a ROA for AS202520, maxLength 48.635 of 636
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS-24IT; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS-CFLD; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS-EURON; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS-INVITEL-UA; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS-LINXTELECOM-PL; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS-NETRES; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS-STUDIOWIK; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS213707:AS-UKNOC-DOWNSTREAM; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS202520:AS-CLIENTSAS202520:AS-CLIENTS (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it.

Route objects not announced

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

93.114.89.0/24RADB, RIPEValid

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.