Network · data from 2026-11-12
AS209604 2E Telekom (TWO E Telekom)
Registry name: TWO-E-Telekom 2E TELEKOMUNIKASYON LTD STI, TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209604, 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.
| 5.10.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.45.45.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.114.183.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.10.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.177.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 108.165.233.0/24 | Valid | RIR databaseARIN | 673 100% |
| 136.175.82.0/24 | Valid | RIR databaseARIN | 673 100% |
| 143.246.43.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 158.51.78.0/24 | Valid | RIR databaseARIN | 673 100% |
| 166.1.2.0/24 | Valid | RIR databaseARIN | 673 100% |
| 179.254.112.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.93.68.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.93.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.93.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.132.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.255.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.255.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.255.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.255.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.36.85.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.39.241.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.253.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.155.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.229.250.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 103.69.3.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 142.111.183.0/24 | Valid | RIR databaseARIN | 672 100% |
| 144.225.54.0/24 | Valid | RIR databaseARIN | 672 100% |
| 208.92.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 72.18.67.0/24 | Valid | RIR databaseARIN | 671 100% |
| 136.175.83.0/24 | Valid | RIR databaseARIN | 671 100% |
| 2.27.72.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 45.39.247.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.26.200.0/24 | Valid | RIR databaseARIN | 669 99% |
| 23.26.203.0/24 | Valid | RIR databaseARIN | 669 99% |
| 23.230.139.0/24 | Valid | RIR databaseARIN | 669 99% |
| 87.58.208.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 87.58.209.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 104.224.53.0/24 | Valid | RIR databaseARIN | 669 99% |
| 104.252.72.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 108.165.191.0/24 | Valid | RIR databaseARIN | 669 99% |
| 108.165.248.0/24 | Valid | RIR databaseARIN | 669 99% |
| 136.0.197.0/24 | Valid | RIR databaseARIN | 669 99% |
| 144.225.55.0/24 | Valid | RIR databaseARIN | 669 99% |
| 162.251.1.0/24 | Valid | RIR databaseARIN | 669 99% |
| 166.1.80.0/24 | Valid | RIR databaseARIN | 669 99% |
| 168.222.182.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 172.252.125.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 179.253.188.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 179.254.94.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.73.127.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.93.71.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.106.199.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 208.92.225.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.38.190.0/24 | Valid | RIR databaseARIN | 668 99% |
| 45.39.103.0/24 | Valid | RIR databaseARIN, RADB | 668 99% |
| 142.249.78.0/24 | Valid | RIR databaseARIN | 668 99% |
| 144.225.53.0/24 | Valid | RIR databaseARIN | 668 99% |
| 45.38.210.0/24 | Valid | RIR databaseARIN | 667 99% |
| 31.77.167.0/24 | Valid | RIR databaseRIPE | 666 99% |
| 104.193.194.0/24 | Valid | RIR databaseARIN | 666 99% |
| 45.38.149.0/24 | Valid | RIR databaseARIN | 665 99% |
| 2a05:f7c0::/32 | Valid | RIR databaseRIPE | 604 95% |
AS-SET
AS209604's PeeringDB record names no AS-SET.
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 2 are in fix.csv.
- Route object: not announced2
Route objects not announced
Route objects with origin AS209604 whose prefix no peer sees AS209604 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 188.132.209.0/24 | RIPE | Valid |
| 213.238.168.0/24 | RIPE | Valid |
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.