Network · data from 2026-11-12
AS205209 Bynet-business BINAT BUSINESS LTD
Registry name: Bynet-business BINAT BUSINESS LTD, IL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205209, 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.
| 94.188.178.0/24 | Valid | Other origin only | 1 0%low visibility |
| 94.188.191.0/24 | Valid | Other origin only | 1 0%low visibility |
| 92.61.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.138.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.140.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.161.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.167.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.188.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.197.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.188.242.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.223.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 80.74.96.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.74.97.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.74.99.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.74.123.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.188.165.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.188.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.188.186.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 94.188.243.0/24 | Valid | RIR databaseRIPE | 33 5%low visibility |
AS-SET
AS205209 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 13 are in fix.csv.
- Route object: none2
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 94.188.178.0/24 | Route objects for it name AS25003. Add a route object with origin AS205209 in the RIR database for the space. |
| Route object: none | 94.188.191.0/24 | Route objects for it name AS25003. Add a route object with origin AS205209 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205209 whose prefix no peer sees AS205209 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 92.61.224.0/24 | RIPE | Valid |
| 92.61.225.0/24 | RIPE | Valid |
| 92.61.234.0/23 | RIPE | Valid |
| 92.61.234.0/24 | RIPE | Valid |
| 92.61.235.0/24 | RIPE | Valid |
| 94.188.171.0/24 | RIPE | Valid |
| 94.188.200.0/24 | RIPE | Valid |
| 94.188.251.0/24 | RIPE | Valid |
| 141.226.250.0/23 | RIPE | Valid |
| 141.226.250.0/24 | RIPE | Valid |
| 2a0d:2800::/29 | 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.