Network · data from 2026-11-12
AS203545 NERZEN BILISIM TEKNOLOJILERI
Registry name: NERZEN-BILISIM-TEKNOLOJILERI Savas Anac, TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203545, 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.
| 23.26.123.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 194.146.26.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 31.77.55.0/24 | Valid | RIR databaseRIPE | 658 98% |
| 141.98.50.0/24 | Valid | RIR databaseRIPE | 658 98% |
| 144.225.64.0/24 | Valid | RIR databaseARIN | 658 98% |
| 166.1.5.0/24 | Valid | RIR databaseARIN | 658 98% |
| 156.233.71.0/24 | Valid | RIR databaseAFRINIC, RADB | 657 98% |
| 185.73.125.0/24 | Valid | RIR databaseRIPE | 651 97% |
| 2a0f:bf01::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS203545: AS203545:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS203545 isn't in the set, or no route object for AS203545 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS203545 in it | Not covered |
|---|---|---|---|---|---|
| AS203545:AS-CUSTOMERS | RIPE | 3 | 1 | Yes | 2 |
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.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 23.26.123.0/24 | ROAs covering it name AS198988, not AS203545. If AS203545 should announce it, add a ROA for AS203545. |
| Route object: none | 23.26.123.0/24 | Route objects for it name AS198988. Add a route object with origin AS203545 in the RIR database for the space. |
| ROA: origin | 194.146.26.0/24 | ROAs covering it name AS44547, AS198988, not AS203545. If AS203545 should announce it, add a ROA for AS203545. |
| Route object: none | 194.146.26.0/24 | Route objects for it name AS44547, AS198988. Add a route object with origin AS203545 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS203545 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.