bgpreport

Network · data from 2026-11-12

AS201618 IBB Istanbul Metropolitan Municipality

Registry name: IBB Istanbul Metropolitan Municipality, TR · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS201618, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201618, 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.
185.68.221.0/24 Valid RIR databaseRIPE 673 100% 67
185.68.222.0/23 Valid RIR databaseRIPE 673 100% 67
185.68.223.0/24 Valid RIR databaseRIPE 673 100% 67
185.68.222.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS201618 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 10 are in fix.csv.

  • Route object: not announced10

Route objects not announced

Route objects with origin AS201618 whose prefix no peer sees AS201618 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.68.220.0/22RIPENo ROA
185.68.220.0/23RIPEValid
185.68.220.0/24RIPEValid
2a05:1d80::/29RIPENo ROA
2a05:1d80::/47RIPENo ROA
2a05:1d80::/48RIPENo ROA
2a05:1d80:1::/48RIPENo ROA
2a05:1d80:2::/47RIPENo ROA
2a05:1d80:2::/48RIPENo ROA
2a05:1d80:3::/48RIPENo 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.