Network · data from 2026-11-12
AS213257 AS213257 Meric Internet Teknolojileri A.S.
Registry name: AS213257 Meric Internet Teknolojileri A.S., TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213257, 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.
| 209.191.168.0/24 | Invalid: origin | None | 3 0%low visibility |
| 5.180.106.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.116.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.136.4.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.83.201.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 209.191.169.0/24 | Valid | RIR databaseARIN | 3 0%low visibility |
| 209.191.170.0/24 | Valid | RIR databaseARIN | 3 0%low visibility |
| 209.191.171.0/24 | Valid | RIR databaseARIN | 3 0%low visibility |
AS-SET
AS213257 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 209.191.168.0/24 | ROAs covering it name AS2914, not AS213257. If AS213257 should announce it, add a ROA for AS213257. |
| Route object: none | 209.191.168.0/24 | No route object for it. Add a route object with origin AS213257 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213257 whose prefix no peer sees AS213257 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.180.107.0/24 | RIPE | Valid |
| 77.83.202.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.