Network · data from 2026-11-12
AS218391 MRSBILISIM-AS MRS BILISIM VE TELEKOMUNIKASYON HIZMETLERI LIMITED SIRKETI
Registry name: MRSBILISIM-AS MRS BILISIM VE TELEKOMUNIKASYON HIZMETLERI LIMITED SIRKETI, TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS218391, 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.
| 154.193.0.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 156.229.60.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.194.8.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.195.231.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.143.98.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.10.151.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.148.240.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS218391 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.
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 154.193.0.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.229.60.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.194.8.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.195.231.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS218391 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.