Network · data from 2026-11-12
AS204209 BIZIMINTERNET BIZIM INTERNET VE BILISIM TEKNOLOJILERI SAN. VE TIC.LTD.STI.
Registry name: BIZIMINTERNET BIZIM INTERNET VE BILISIM TEKNOLOJILERI SAN. VE TIC.LTD.STI., TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204209, 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.
| 31.145.39.0/24 | Valid | Other origin only | 673 100% |
| 185.249.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.249.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.249.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.249.89.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS204209 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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 31.145.39.0/24 | Route objects for it name AS15924. Add a route object with origin AS204209 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS204209 whose prefix no peer sees AS204209 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.249.88.0/22 | RIPE | No ROA |
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.