Network · data from 2026-11-12
AS216472 HS-SYR High Speed For Internet Services L.L.C
Registry name: HS-SYR High Speed For Internet Services L.L.C, SY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216472, 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.
| 139.28.49.0/24 | Invalid: origin | None | 2 0%low visibility |
| 193.93.54.0/24 | Invalid: origin | None | 2 0%low visibility |
| 103.17.202.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 131.222.253.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 79.98.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.189.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.189.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.232.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.43.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.251.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 153.56.246.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.132.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.132.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 191.44.71.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 191.44.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 191.44.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.33.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.5.168.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.62.50.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 201.4.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 201.4.68.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 201.7.29.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 201.7.31.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.68.59.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.98.34.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 153.56.247.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 191.44.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 201.4.70.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 201.7.28.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.76.138.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.43.133.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.43.134.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.43.135.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.224.242.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 116.204.166.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.254.55.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 191.44.88.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 191.44.127.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 201.4.71.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 205.234.123.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.18.211.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 222.167.236.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.149.24.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 128.0.7.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 201.4.64.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 201.4.69.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 45.198.85.0/24 | Valid | RIR databaseAFRINIC, RADB | 656 97% |
| 2a0b:3840::/29 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS216472 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 11 are in fix.csv.
- ROA: origin4
- Route object: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 139.28.49.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS216472 should announce it, add a ROA for AS216472. |
| Route object: none | 139.28.49.0/24 | No route object for it. Add a route object with origin AS216472 in the RIR database for the space. |
| ROA: origin | 193.93.54.0/24 | ROAs covering it name AS34346, not AS216472. If AS216472 should announce it, add a ROA for AS216472. |
| Route object: none | 193.93.54.0/24 | No route object for it. Add a route object with origin AS216472 in the RIR database for the space. |
| ROA: origin | 103.17.202.0/24 | ROAs covering it name AS200464, not AS216472. If AS216472 should announce it, add a ROA for AS216472. |
| Route object: none | 103.17.202.0/24 | Route objects for it name AS200464. Add a route object with origin AS216472 in the RIR database for the space. |
| ROA: origin | 131.222.253.0/24 | ROAs covering it name AS34984, not AS216472. If AS216472 should announce it, add a ROA for AS216472. |
| Route object: none | 131.222.253.0/24 | Route objects for it name AS34984. Add a route object with origin AS216472 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS216472 whose prefix no peer sees AS216472 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.196.101.0/24 | AFRINIC, RADB | Valid |
| 128.0.4.0/24 | RIPE | Valid |
| 201.4.75.0/24 | 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.