Network · data from 2026-11-12
AS203248 BurtiNET
Registry name: BurtiNET BNET BULUT Bilisim Hizmetleri Tic. Ltd. Sti., TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203248, 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.
| 146.19.208.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 167.160.4.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.165.46.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a0a:7580::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:1::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:2::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:3::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:4::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:5::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:6::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:7::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:8::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:9::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:a::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:b::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:c::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:d::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:e::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:f::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:7580:10::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS203248's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS203248 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.