Network · data from 2026-11-12
AS209737 Meric Internet Teknolojileri
Registry name: AS209737 Meric Internet Teknolojileri A.S., TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209737, 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.
| 176.96.128.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 5.180.105.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.180.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.40.205.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.249.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.249.62.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.236.49.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.111.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.74.242.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.83.200.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.254.31.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 77.83.202.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 2a05:dfc3:fd30::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a09:8780::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:b700::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:e900::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:eb00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:ed00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:f900::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a13:a440:7::/48 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:a441::/32 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:a442::/32 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:a443::/32 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:a444::/32 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:a445::/32 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:a446::/32 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:a447::/32 | Valid | RIR databaseRIPE | 632 99% |
| 85.235.73.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS209737'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 24 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 176.96.128.0/24 | ROAs covering it name AS215238, not AS209737. If AS209737 should announce it, add a ROA for AS209737. |
| Route object: none | 176.96.128.0/24 | Route objects for it name AS215238. Add a route object with origin AS209737 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS209737 whose prefix no peer sees AS209737 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.180.106.0/24 | RIPE | Valid |
| 45.74.176.0/24 | RIPE | Valid |
| 45.136.4.0/24 | RIPE | Valid |
| 77.83.201.0/24 | RADB, RIPE | Valid |
| 89.116.44.0/22 | RIPE | No ROA |
| 89.116.126.0/23 | RIPE | Valid |
| 89.116.212.0/22 | RIPE | No ROA |
| 89.117.104.0/22 | RIPE | Valid |
| 89.117.152.0/22 | RIPE | Valid |
| 104.234.156.0/22 | ARIN | No ROA |
| 111.235.150.0/24 | RIPE | Valid |
| 140.99.44.0/22 | ARIN | Valid |
| 140.99.180.0/22 | ARIN | Valid |
| 140.99.208.0/22 | ARIN | Valid |
| 185.254.28.0/24 | RIPE | Valid |
| 191.96.146.0/23 | RIPE | No ROA |
| 191.101.20.0/23 | RIPE | No ROA |
| 191.101.126.0/23 | RIPE | Invalid: origin |
| 194.116.237.0/24 | RIPE | Valid |
| 217.18.208.0/24 | RIPE | Valid |
| 2a0f:eb07::/32 | RIPE | Valid |
| 2a0f:ed03::/32 | 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.