Network · data from 2026-11-12
AS51557 TR-ISIMTESCIL-20201202 Isimtescil Bilisim A.S.
Registry name: TR-ISIMTESCIL-20201202 Isimtescil Bilisim A.S., TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51557, 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.
| 84.51.21.0/24 | Valid | None | 673 100% |
| 84.51.25.0/24 | Valid | None | 673 100% |
| 84.51.38.0/24 | Valid | None | 673 100% |
| 91.93.146.0/24 | Valid | None | 673 100% |
| 91.93.149.0/24 | Valid | None | 673 100% |
| 91.93.151.0/24 | Valid | Other origin only | 673 100% |
| 91.93.152.0/24 | Valid | None | 673 100% |
| 93.89.224.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.33.232.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.111.232.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.111.234.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a00:e5c0::/32 | Valid | RIR databaseRIPE | 629 99% |
AS-SET
AS51557 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 13 are in fix.csv.
- Route object: none7
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 84.51.21.0/24 | No route object for it. Add a route object with origin AS51557 in the RIR database for the space. |
| Route object: none | 84.51.25.0/24 | No route object for it. Add a route object with origin AS51557 in the RIR database for the space. |
| Route object: none | 84.51.38.0/24 | No route object for it. Add a route object with origin AS51557 in the RIR database for the space. |
| Route object: none | 91.93.146.0/24 | No route object for it. Add a route object with origin AS51557 in the RIR database for the space. |
| Route object: none | 91.93.149.0/24 | No route object for it. Add a route object with origin AS51557 in the RIR database for the space. |
| Route object: none | 91.93.151.0/24 | Route objects for it name AS34104, AS34984. Add a route object with origin AS51557 in the RIR database for the space. |
| Route object: none | 91.93.152.0/24 | No route object for it. Add a route object with origin AS51557 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51557 whose prefix no peer sees AS51557 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.89.224.0/24 | RIPE | Invalid: maxLength |
| 93.89.225.0/24 | RIPE | Invalid: maxLength |
| 93.89.226.0/24 | RIPE | Invalid: maxLength |
| 93.89.227.0/24 | RIPE | Invalid: maxLength |
| 93.89.228.0/24 | RIPE | Invalid: maxLength |
| 93.89.229.0/24 | RIPE | Invalid: maxLength |
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.