Network · data from 2026-11-12
AS201550 EXT-PDN-STE-AS Syrian Telecommunication Private Closed Joint Stock Company
Registry name: EXT-PDN-STE-AS Syrian Telecommunication Private Closed Joint Stock Company, SY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201550, 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.
| 178.169.0.0/23 | Valid | Nonecovered by 178.169.0.0/20 | 671 100% |
| 193.124.28.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.124.72.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.124.82.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 94.47.128.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 94.47.160.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 94.47.192.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 94.47.224.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 188.133.0.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 188.133.16.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 188.133.32.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 188.133.48.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 188.133.64.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 188.133.80.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 188.133.96.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 188.133.112.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 193.124.10.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 193.124.12.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 193.124.26.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 193.124.192.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 5.0.192.0/19 | Valid | RIR databaseRIPE | 668 99% |
| 5.0.224.0/21 | Valid | RIR databaseRIPE | 668 99% |
| 5.0.232.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 5.0.234.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 5.0.236.0/22 | Valid | RIR databaseRIPE | 668 99% |
| 5.0.240.0/20 | Valid | RIR databaseRIPE | 668 99% |
| 5.155.224.0/21 | Valid | RIR databaseRIPE | 668 99% |
| 5.155.232.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 5.155.234.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 5.155.236.0/22 | Valid | RIR databaseRIPE | 668 99% |
| 5.155.240.0/20 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.128.0/19 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.160.0/21 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.168.0/22 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.172.0/22 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.176.0/20 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.192.0/19 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.224.0/21 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.232.0/22 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.236.0/22 | Valid | RIR databaseRIPE | 668 99% |
| 31.9.240.0/20 | Valid | RIR databaseRIPE | 668 99% |
| 193.124.62.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 193.124.68.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 193.124.96.0/21 | Valid | RIR databaseRIPE | 668 99% |
| 193.124.104.0/22 | Valid | RIR databaseRIPE | 668 99% |
| 193.124.108.0/22 | Valid | RIR databaseRIPE | 668 99% |
| 193.124.160.0/21 | Valid | RIR databaseRIPE | 668 99% |
| 193.124.168.0/21 | Valid | RIR databaseRIPE | 668 99% |
| 5.155.192.0/19 | Valid | RIR databaseRIPE | 373 55% |
| 193.124.216.0/23 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 193.124.218.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 193.124.219.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 193.124.220.0/22 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 194.58.0.0/21 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 194.58.8.0/23 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 194.58.11.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 194.58.12.0/22 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS201550 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 6 are in fix.csv.
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 178.169.0.0/23 | No route object for it. A route object for 178.169.0.0/20 with origin AS201550 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201550 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201550 whose prefix no peer sees AS201550 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.169.0.0/20 | RIPE | No ROA |
| 193.124.96.0/22 | RIPE | Invalid: maxLength |
| 193.124.208.0/21 | RIPE | Valid |
| 194.58.10.0/24 | RIPE | Valid |
| 194.135.106.0/23 | 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.