bgpreport

Network · data from 2026-11-12

AS206963 SprintCDN

Registry name: SprintCDN SPRINTCDN LLC, UA · PeeringDB

7IPv4 routes 57.1% RPKI valid · 100.0% with a route object
0IPv6 routes
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 AS206963, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS206963, 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.
185.248.170.0/24 No ROA RIR databaseRIPE 671 100% 68
185.248.169.0/24 No ROA RIR databaseRIPE 668 99% 68
185.248.171.0/24 No ROA RIR databaseRIPE 668 99% 68
62.76.227.0/24 Valid RIR databaseRIPE 671 100% 68
80.71.230.0/24 Valid RIR databaseRIPE 671 100% 68
93.88.202.0/24 Valid RIR databaseRIPE 671 100% 68
89.125.36.0/24 Valid RIR databaseRIPE 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS206963: AS206963:AS-SPRINTCDN. 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 (AS206963 isn't in the set, or no route object for AS206963 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 objectsAS206963 in itNot covered
AS206963:AS-SPRINTCDN RIPElists itself further down5 member sets in no database: AS-24IT, AS-EURON, AS-INVITEL-UA, AS-LINXTELECOM-PL, AS-NETRES 1,28212714,922 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 9 are in fix.csv.

  • ROA: none3
  • AS-SET: missing member5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.248.170.0/24No ROA covers it. Add a ROA for AS206963, maxLength 24.671 of 673
ROA: none185.248.169.0/24No ROA covers it. Add a ROA for AS206963, maxLength 24.668 of 673
ROA: none185.248.171.0/24No ROA covers it. Add a ROA for AS206963, maxLength 24.668 of 673
AS-SET: missing memberAS206963:AS-SPRINTCDNAS206963:AS-SPRINTCDN (RIPE) lists AS-24IT; no IRR database read has it.
AS-SET: missing memberAS206963:AS-SPRINTCDNAS206963:AS-SPRINTCDN (RIPE) lists AS-EURON; no IRR database read has it.
AS-SET: missing memberAS206963:AS-SPRINTCDNAS206963:AS-SPRINTCDN (RIPE) lists AS-INVITEL-UA; no IRR database read has it.
AS-SET: missing memberAS206963:AS-SPRINTCDNAS206963:AS-SPRINTCDN (RIPE) lists AS-LINXTELECOM-PL; no IRR database read has it.
AS-SET: missing memberAS206963:AS-SPRINTCDNAS206963:AS-SPRINTCDN (RIPE) lists AS-NETRES; no IRR database read has it.

Route objects not announced

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

2001:470:507::/48ARINValid

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.