AS50300CustodianDC Limited
As of 10th November 2026, AS50300 (CustodianDC Limited), a content network registered in the United Kingdom with RIPE NCC, originates 39 IPv4 prefixes covering 10.8k addresses and 7 IPv6 prefixes. By IPv4 address space that makes it the 10,253rd-largest of the 80,723 networks we see originating IPv4, and the 314th-largest of 2,122 in the United Kingdom. It is seen behind 41 upstream networks, most often AS2914 (NTT America, Inc.) and AS3356 (Lumen (Level 3)), and in front of 6 downstream networks. 96% of its announcements have a valid RPKI ROA, and none are RPKI-invalid. 100% of its routes reach at least 90% of full-feed peers.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS50300 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS50300 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.
Neighbouring networks
1,212
adjacent networks
- Upstreams
- 413%
- Peers
- 1,16596%
- Downstreams
- 60%
Networks carrying this one's traffic toward the rest of the internet. Listing the 40 seen on the most AS paths, of 41.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS2914NTT America, Inc. | Peer | 987 | 32 | |
| AS3356Lumen (Level 3) | Peer | 574 | 22 | |
| AS174Cogent Communications, LLC | Peer | 435 | 13 | |
| AS6939Hurricane Electric LLC | Peer | 344 | 37 | |
| AS3257GTT Communications Inc. | Peer | 215 | 38 | |
| AS9002RETN Limited | Peer | 181 | 5 | |
| AS13030Init7 (Switzerland) Ltd. | Peer | 130 | 4 | |
| AS18106Viewqwest Pte Ltd | Peer | 105 | 2 | |
| AS14537Continent 8 LLC | Peer | 103 | 2 | |
| AS25091IP-Max SA | Peer | 69 | 3 |
Prefixes
All 46The largest blocks AS50300 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 185.14.164.0/22 | 1k | 76/76 |
| 5.102.168.0/24 | 256 | 76/76 |
| 5.102.169.0/24 | 256 | 76/76 |
| 5.102.170.0/24 | 256 | 76/76 |
| 5.102.171.0/24 | 256 | 76/76 |
| 5.102.172.0/24 | 256 | 76/76 |
| 5.102.173.0/24 | 256 | 76/76 |
| 5.102.174.0/24 | 256 | 76/76 |
| 5.102.175.0/24 | 256 | 76/76 |
| 92.118.16.0/24 | 256 | 76/76 |
Routing health
How AS50300's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.
RPKI origin validation
- Valid95.7%44
- Invalid0.0%0
- No ROA4.3%2
Propagation
- Globally propagated90% of full-feed peers or more100.0%46
- Partially propagated40% to 90%0.0%0
- Seen by few peersUnder 40%0.0%0
Prefix sizes
IPv4 — 39 prefixes
IPv6 — 7 prefixes
- /4016.8M × /6414.3%1
- /441M × /6471.4%5
- /4865.5k × /6414.3%1
Recent changes
Announcements that started or stopped since 11th Oct 2026.
No announcement by AS50300 started or stopped in this period.
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.