AS20919DataFort LLC
As of 11th November 2026, AS20919 (DataFort LLC), a network registered in Russia with RIPE NCC, originates 13 IPv4 prefixes covering 9.5k addresses. By IPv4 address space that makes it the 11,026th-largest of the 80,743 networks we see originating IPv4, and the 614th-largest of 4,983 in Russia. It is seen behind 5 upstream networks, most often AS12389 (PJSC Rostelecom) and AS20485 (JSC TransTeleCom), and in front of 2 downstream networks. None of its announcements have a valid RPKI ROA. 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 AS20919 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS20919 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
14
adjacent networks
- Upstreams
- 536%
- Peers
- 750%
- Downstreams
- 214%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS12389PJSC Rostelecom | Peer | 349 | 28 | |
| AS20485JSC TransTeleCom | Peer | 310 | 32 | |
| AS3216PJSC Vimpelcom | Peer | 222 | 29 | |
| AS57304RETN Russia | Peer | 167 | 34 | |
| AS31133PJSC MegaFon | Peer | 36 | 4 |
Prefixes
The largest blocks AS20919 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 217.74.32.0/21 | 2k | 76/76 |
| 217.198.80.0/21 | 2k | 76/76 |
| 217.74.40.0/22 | 1k | 76/76 |
| 217.198.88.0/22 | 1k | 76/76 |
| 46.42.134.0/23 | 512 | 76/76 |
| 77.41.188.0/23 | 512 | 76/76 |
| 81.222.150.0/23 | 512 | 76/76 |
| 217.74.46.0/23 | 512 | 76/76 |
| 217.74.44.0/24 | 256 | 76/76 |
| 217.74.45.0/24 | 256 | 76/76 |
Routing health
How AS20919'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
- Valid0.0%0
- Invalid0.0%0
- No ROA100.0%13
Propagation
- Globally propagated90% of full-feed peers or more100.0%13
- Partially propagated40% to 90%0.0%0
- Seen by few peersUnder 40%0.0%0
Prefix sizes
Recent changes
Announcements that started or stopped since 12th Oct 2026.
- Announced46.42.134.0/2320th Oct 2026
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.