bgpreport

Network · data from 2026-11-12

AS11251 Disney Streaming Origin

Registry name: DSTL-2-11251 - Disney Streaming Services, US · PeeringDB

18IPv4 routes 94.4% RPKI valid · 50.0% with a route object
11IPv6 routes 81.8% RPKI valid · 72.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 12 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS11251, seen from no peer

Announced routes

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

2405:dc0:8008::/48 No ROA Other origin onlycovered by 2405:dc0:8000::/40 635 100% 68
8.5.5.0/24 No ROA Other IRR onlyRADB 672 100% 67
2405:dc0:8001::/48 No ROA Other IRR onlyRADB 634 100% 68
139.104.126.0/24 Valid Nonecovered by 139.104.96.0/19 672 100% 67
139.104.194.0/24 Valid Nonecovered by 139.104.192.0/21 672 100% 67
139.104.200.0/24 Valid Nonecovered by 139.104.200.0/22 672 100% 67
139.104.201.0/24 Valid Nonecovered by 139.104.200.0/22 672 100% 67
139.104.202.0/24 Valid Nonecovered by 139.104.200.0/22 672 100% 67
139.104.203.0/24 Valid Nonecovered by 139.104.200.0/22 672 100% 67
139.104.208.0/24 Valid Other origin onlycovered by 139.104.192.0/19 672 100% 67
139.104.204.0/24 Valid Nonecovered by 139.104.204.0/22 670 100% 67
2620:138:3007::/48 Valid Nonecovered by 2620:138:3000::/44 635 100% 68
139.104.192.0/24 Valid Nonecovered by 139.104.192.0/21 3 0%low visibility 3
2620:138:3002::/48 Valid Nonecovered by 2620:138:3000::/44 2 0%low visibility 2
139.104.124.0/24 Valid Other IRR onlyRADB 672 100% 67
139.104.197.0/24 Valid Other IRR onlyRADB 672 100% 67
139.104.199.0/24 Valid Other IRR onlyRADB 672 100% 67
157.23.225.0/24 Valid Other IRR onlyRADB 672 100% 67
139.104.198.0/24 Valid Other IRR onlyRADB 671 100% 67
157.23.224.0/24 Valid Other IRR onlyRADB 671 100% 67
139.104.125.0/24 Valid Other IRR onlyRADB 670 100% 67
139.104.195.0/24 Valid Other IRR onlyRADB 670 100% 67
2620:138:3000::/48 Valid Other IRR onlyRADB 636 100% 67
2620:138:3001::/48 Valid Other IRR onlyRADB 636 100% 67
2620:138:3020::/48 Valid Other IRR onlyRADB 636 100% 67
2a0e:bbc0:8000::/48 Valid Other IRR onlyRADB 634 100% 68
2620:138:3006::/48 Valid Other IRR onlyRADB 633 100% 68
2a0e:bbc0:8001::/48 Valid Other IRR onlyRADB 605 95% 67
2620:138:300f::/48 Valid RIR databaseARIN 634 100% 68

AS-SET

PeeringDB's irr_as_set for AS11251: AS-DSS-ALL. 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 (AS11251 isn't in the set, or no route object for AS11251 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 objectsAS11251 in itNot covered
AS-DSS-ALL RADB 61166 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 45 are in fix.csv.

  • ROA: none3
  • Route object: none12
  • Route object: RIR16
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none2405:dc0:8008::/48No ROA covers it. Add a ROA for AS11251, maxLength 48.635 of 636
Route object: none2405:dc0:8008::/48Route objects for it name AS22604. A route object for 2405:dc0:8000::/40 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.635 of 636
ROA: none8.5.5.0/24No ROA covers it. Add a ROA for AS11251, maxLength 24.672 of 673
Route object: RIR8.5.5.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2405:dc0:8001::/48No ROA covers it. Add a ROA for AS11251, maxLength 48.634 of 636
Route object: RIR2405:dc0:8001::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: none139.104.126.0/24No route object for it. A route object for 139.104.96.0/19 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.672 of 673
Route object: none139.104.194.0/24No route object for it. A route object for 139.104.192.0/21 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.672 of 673
Route object: none139.104.200.0/24No route object for it. A route object for 139.104.200.0/22 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.672 of 673
Route object: none139.104.201.0/24No route object for it. A route object for 139.104.200.0/22 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.672 of 673
Route object: none139.104.202.0/24No route object for it. A route object for 139.104.200.0/22 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.672 of 673
Route object: none139.104.203.0/24No route object for it. A route object for 139.104.200.0/22 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.672 of 673
Route object: none139.104.208.0/24Route objects for it name AS22604. A route object for 139.104.192.0/19 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.672 of 673
Route object: none139.104.204.0/24No route object for it. A route object for 139.104.204.0/22 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.670 of 673
Route object: none2620:138:3007::/48No route object for it. A route object for 2620:138:3000::/44 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.635 of 636
Route object: none139.104.192.0/24No route object for it. A route object for 139.104.192.0/21 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.3 of 673
Route object: none2620:138:3002::/48No route object for it. A route object for 2620:138:3000::/44 with origin AS11251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11251 in the RIR database for the space.2 of 636
Route object: RIR139.104.124.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.104.197.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.104.199.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR157.23.225.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.104.198.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR157.23.224.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR139.104.125.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR139.104.195.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2620:138:3000::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2620:138:3001::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2620:138:3020::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a0e:bbc0:8000::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2620:138:3006::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2a0e:bbc0:8001::/48Route object only in RADB. Add it in the RIR database for the space.605 of 636

Route objects not announced

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

139.104.96.0/19RADBValid
139.104.96.0/24RADBValid
139.104.192.0/19RADBValid
139.104.192.0/21ARINValid
139.104.200.0/22ARIN, RADBValid
139.104.204.0/22ARIN, RADBValid
157.23.224.0/20RADBValid
2405:dc0:8000::/40RADBNo ROA
2405:dc0:8000::/48RADBNo ROA
2620:138:3000::/40ARIN, RADBValid
2620:138:3000::/44ARINValid
2620:138:3003::/48RADBValid
2620:138:30fe::/48RADBValid
2a0e:bbc0:8000::/40RADBValid

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.