Network · data from 2026-11-12
AS57844 SPDNet Telekomunikasyon
Registry name: SPD-Net SPDNet Telekomunikasyon Hizmetleri Bilgi Teknolojileri Taahhut Sanayi Ve Ticaret A.S., TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57844, 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.
| 37.123.96.0/24 | Valid | Nonecovered by 37.123.96.0/21 | 671 100% |
| 37.123.98.0/24 | Valid | Nonecovered by 37.123.96.0/21 | 671 100% |
| 37.123.101.0/24 | Valid | Nonecovered by 37.123.96.0/21 | 671 100% |
| 139.28.73.0/24 | Valid | Nonecovered by 139.28.72.0/22 | 671 100% |
| 139.28.74.0/24 | Valid | Nonecovered by 139.28.72.0/22 | 671 100% |
| 139.28.75.0/24 | Valid | Nonecovered by 139.28.72.0/22 | 671 100% |
| 178.20.225.0/24 | Valid | Nonecovered by 178.20.224.0/21 | 671 100% |
| 178.20.227.0/24 | Valid | Nonecovered by 178.20.224.0/21 | 671 100% |
| 178.20.231.0/24 | Valid | Nonecovered by 178.20.224.0/21 | 671 100% |
| 185.204.16.0/24 | Valid | Nonecovered by 185.204.16.0/22 | 671 100% |
| 185.204.17.0/24 | Valid | Nonecovered by 185.204.16.0/22 | 671 100% |
| 185.204.18.0/24 | Valid | Nonecovered by 185.204.16.0/22 | 671 100% |
| 185.204.19.0/24 | Valid | Nonecovered by 185.204.16.0/22 | 671 100% |
| 37.123.97.0/24 | Valid | Nonecovered by 37.123.96.0/21 | 2 0%low visibility |
| 178.20.228.0/24 | Valid | Nonecovered by 178.20.224.0/21 | 2 0%low visibility |
| 178.20.229.0/24 | Valid | Nonecovered by 178.20.224.0/21 | 2 0%low visibility |
| 185.118.142.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.9.156.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 185.9.157.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 185.9.158.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 185.118.143.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a00:9bc0::/32 | Valid | RIR databaseRIPE | 634 100% |
| 23.247.179.0/24 | Valid | RIR databaseARIN | 3 0%low visibility |
| 23.247.176.0/24 | Valid | RIR databaseARIN | 2 0%low visibility |
| 23.247.177.0/24 | Valid | RIR databaseARIN | 2 0%low visibility |
| 23.247.178.0/24 | Valid | RIR databaseARIN | 2 0%low visibility |
| 185.9.159.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS57844: AS-SPDNET. 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 (AS57844 isn't in the set, or no route object for AS57844 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 | AS57844 in it | Not covered |
|---|---|---|---|---|---|
| AS-SPDNET | RIPE | 6 | 1 | Yes | 0 |
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 32 are in fix.csv.
- Route object: none16
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 37.123.96.0/24 | No route object for it. A route object for 37.123.96.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 37.123.98.0/24 | No route object for it. A route object for 37.123.96.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 37.123.101.0/24 | No route object for it. A route object for 37.123.96.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 139.28.73.0/24 | No route object for it. A route object for 139.28.72.0/22 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 139.28.74.0/24 | No route object for it. A route object for 139.28.72.0/22 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 139.28.75.0/24 | No route object for it. A route object for 139.28.72.0/22 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 178.20.225.0/24 | No route object for it. A route object for 178.20.224.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 178.20.227.0/24 | No route object for it. A route object for 178.20.224.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 178.20.231.0/24 | No route object for it. A route object for 178.20.224.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 185.204.16.0/24 | No route object for it. A route object for 185.204.16.0/22 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 185.204.17.0/24 | No route object for it. A route object for 185.204.16.0/22 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 185.204.18.0/24 | No route object for it. A route object for 185.204.16.0/22 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 185.204.19.0/24 | No route object for it. A route object for 185.204.16.0/22 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 37.123.97.0/24 | No route object for it. A route object for 37.123.96.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 178.20.228.0/24 | No route object for it. A route object for 178.20.224.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
| Route object: none | 178.20.229.0/24 | No route object for it. A route object for 178.20.224.0/21 with origin AS57844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57844 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS57844 whose prefix no peer sees AS57844 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.247.176.0/22 | ARIN | Valid |
| 37.123.96.0/21 | RIPE | No ROA |
| 80.254.232.0/21 | RIPE | Valid |
| 83.147.214.0/23 | RIPE | Invalid: origin |
| 89.249.138.0/24 | RIPE | No ROA |
| 89.249.139.0/24 | RIPE | No ROA |
| 89.249.140.0/24 | RIPE | No ROA |
| 89.249.141.0/24 | RIPE | No ROA |
| 89.249.142.0/24 | RIPE | No ROA |
| 89.249.143.0/24 | RIPE | No ROA |
| 139.28.72.0/22 | RIPE | Valid |
| 178.20.224.0/21 | RIPE | No ROA |
| 185.118.140.0/24 | RIPE | Valid |
| 185.204.16.0/22 | RIPE | Valid |
| 185.220.28.0/22 | RIPE | Valid |
| 193.16.12.0/22 | RIPE | Valid |
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.