Network · data from 2026-11-12
AS209101 ipvendettainc IP Vendetta Inc.
Registry name: ipvendettainc IP Vendetta Inc., SC · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209101, 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.
| 85.11.182.0/24 | Valid | Other origin only | 672 100% |
| 85.11.190.0/24 | Valid | Other origin only | 672 100% |
| 91.92.35.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.26.81.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.154.172.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.95.156.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.95.159.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.151.91.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.26.104.0/24 | Valid | RIR databaseRIPE | 667 99% |
AS-SET
AS209101 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 2 are in fix.csv.
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 85.11.182.0/24 | Route objects for it name AS49870. Add a route object with origin AS209101 in the RIR database for the space. |
| Route object: none | 85.11.190.0/24 | Route objects for it name AS49870. Add a route object with origin AS209101 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS209101 is announced.
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.