bgpreport

Network · data from 2026-11-12

AS3249 Telia Eesti

Registry name: ESTPAK Telia Eesti AS, EE · PeeringDB

31IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS3249, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS3249, 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.
37.157.64.0/18 Valid RIR databaseRIPE 673 100% 67
46.131.0.0/16 Valid RIR databaseRIPE 673 100% 67
62.65.32.0/19 Valid RIR databaseRIPE 673 100% 67
78.110.36.0/22 Valid RIR databaseRIPE 673 100% 67
78.110.40.0/22 Valid RIR databaseRIPE 673 100% 67
80.235.0.0/17 Valid RIR databaseRIPE 673 100% 67
81.20.144.0/20 Valid RIR databaseRIPE 673 100% 67
83.166.32.0/19 Valid RIR databaseRIPE 673 100% 67
84.50.0.0/16 Valid RIR databaseRIPE 673 100% 67
85.29.192.0/18 Valid RIR databaseRIPE 673 100% 67
88.196.0.0/16 Valid RIR databaseRIPE 673 100% 67
89.221.64.0/21 Valid RIR databaseRIPE 673 100% 67
90.190.0.0/15 Valid RIR databaseRIPE 673 100% 67
91.236.222.0/24 Valid RIR databaseRIPE 673 100% 67
94.246.192.0/20 Valid RIR databaseRIPE 673 100% 67
94.246.208.0/21 Valid RIR databaseRIPE 673 100% 67
176.46.0.0/17 Valid RIR databaseRIPE 673 100% 67
185.20.56.0/22 Valid RIR databaseRIPE 673 100% 67
185.40.236.0/22 Valid RIR databaseRIPE 673 100% 67
185.43.104.0/22 Valid RIR databaseRIPE 673 100% 67
194.106.96.0/19 Valid RIR databaseRIPE 673 100% 67
194.126.96.0/19 Valid RIR databaseRIPE 673 100% 67
195.50.192.0/19 Valid RIR databaseRIPE 673 100% 67
195.50.224.0/19 Valid RIR databaseRIPE 673 100% 67
195.250.160.0/19 Valid RIR databaseRIPE 673 100% 67
213.35.128.0/17 Valid RIR databaseRIPE 673 100% 67
213.168.0.0/19 Valid RIR databaseRIPE 673 100% 67
213.180.0.0/19 Valid RIR databaseRIPE 673 100% 67
213.219.64.0/18 Valid RIR databaseRIPE 673 100% 67
217.71.32.0/20 Valid RIR databaseRIPE 673 100% 67
217.159.128.0/17 Valid RIR databaseRIPE 673 100% 67
2001:7d0::/32 Valid RIR databaseRIPE 635 100% 67
2a00:16e0::/32 Valid RIR databaseRIPE 635 100% 67
2a01:158::/32 Valid RIR databaseRIPE 635 100% 67
2a01:6da0::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS3249: RIPE::AS-ESTPAK. 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 (AS3249 isn't in the set, or no route object for AS3249 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 objectsAS3249 in itNot covered
RIPE::AS-ESTPAK RIPE 767802 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS3249 is announced.

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.