AS47205Telia Lietuva, AB
As of 11th November 2026, AS47205 (Telia Lietuva, AB), a network registered in Lithuania with RIPE NCC, originates 1 IPv4 prefix covering 256 addresses. By IPv4 address space that makes it the 59,976th-largest of the 80,743 networks we see originating IPv4, and the 129th-largest of 175 in Lithuania. It is seen behind 1 upstream network, most often AS43811 (Telia Lietuva, AB). Every one of its announcements has 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 AS47205 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS47205 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
3
adjacent networks
- Upstreams
- 133%
- Peers
- 267%
- Downstreams
- 00%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS43811Telia Lietuva, AB | Peer | 75 | 75 |
Prefixes
The largest blocks AS47205 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 195.12.186.0/24 | 256 | 75/76 |
Routing health
How AS47205'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
- Valid100.0%1
- Invalid0.0%0
- No ROA0.0%0
Propagation
- Globally propagated90% of full-feed peers or more100.0%1
- Partially propagated40% to 90%0.0%0
- Seen by few peersUnder 40%0.0%0
Prefix sizes
IPv4 — 1 prefixes
Recent changes
Announcements that started or stopped since 12th Oct 2026.
No announcement by AS47205 started or stopped in this period.
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.