Network · data from 2026-11-12
AS44679 BinBox-Global-Services INVITE Systems SRL
Registry name: BinBox-Global-Services INVITE Systems SRL, RO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44679, 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.
| 81.180.242.0/24 | No ROA | Nonecovered by 81.180.240.0/21 | 670 100% |
| 81.180.243.0/24 | No ROA | Nonecovered by 81.180.240.0/21 | 670 100% |
| 81.180.244.0/24 | No ROA | Nonecovered by 81.180.240.0/21 | 670 100% |
| 81.180.240.0/21 | No ROA | RIR databaseRIPE | 670 100% |
| 84.239.4.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.8.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.9.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.11.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.13.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.14.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.15.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.32.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.34.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.35.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.36.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.38.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.39.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.40.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.44.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.49.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.55.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.56.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.57.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.58.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.59.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.193.52.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.193.53.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.193.54.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.201.232.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.51.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a02:2160:8000::/36 | Valid | RIR databaseRIPE | 635 100% |
| 84.239.29.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS44679 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 10 are in fix.csv.
- ROA: none4
- Route object: none3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 81.180.242.0/24 | No ROA covers it. Add a ROA for AS44679, maxLength 24. |
| Route object: none | 81.180.242.0/24 | No route object for it. A route object for 81.180.240.0/21 with origin AS44679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44679 in the RIR database for the space. |
| ROA: none | 81.180.243.0/24 | No ROA covers it. Add a ROA for AS44679, maxLength 24. |
| Route object: none | 81.180.243.0/24 | No route object for it. A route object for 81.180.240.0/21 with origin AS44679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44679 in the RIR database for the space. |
| ROA: none | 81.180.244.0/24 | No ROA covers it. Add a ROA for AS44679, maxLength 24. |
| Route object: none | 81.180.244.0/24 | No route object for it. A route object for 81.180.240.0/21 with origin AS44679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44679 in the RIR database for the space. |
| ROA: none | 81.180.240.0/21 | No ROA covers it. Add a ROA for AS44679, maxLength 21. |
Route objects not announced
Route objects with origin AS44679 whose prefix no peer sees AS44679 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.193.52.0/22 | RIPE | No ROA |
| 185.193.55.0/24 | RIPE | Valid |
| 2a02:2160:8233::/48 | RIPE | Invalid: maxLength |
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.