Network · data from 2026-11-12
AS6761 INGATE Invest Development LLC
Registry name: INGATE Invest Development LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS6761, 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.
| 2a0b:5d40::/31 | No ROA | Nonecovered by 2a0b:5d40::/30 | 634 100% |
| 2a0b:5d42::/31 | No ROA | Nonecovered by 2a0b:5d40::/30 | 634 100% |
| 2a0b:5d44::/31 | No ROA | Nonecovered by 2a0b:5d44::/30 | 634 100% |
| 2a0b:5d46::/31 | No ROA | Nonecovered by 2a0b:5d44::/30 | 634 100% |
| 94.77.64.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 94.77.64.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 94.77.96.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 185.210.240.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.210.240.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.210.241.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.210.242.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.210.243.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS6761 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 23 are in fix.csv.
- ROA: none12
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0b:5d40::/31 | No ROA covers it. Add a ROA for AS6761, maxLength 31. |
| Route object: none | 2a0b:5d40::/31 | No route object for it. A route object for 2a0b:5d40::/30 with origin AS6761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6761 in the RIR database for the space. |
| ROA: none | 2a0b:5d42::/31 | No ROA covers it. Add a ROA for AS6761, maxLength 31. |
| Route object: none | 2a0b:5d42::/31 | No route object for it. A route object for 2a0b:5d40::/30 with origin AS6761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6761 in the RIR database for the space. |
| ROA: none | 2a0b:5d44::/31 | No ROA covers it. Add a ROA for AS6761, maxLength 31. |
| Route object: none | 2a0b:5d44::/31 | No route object for it. A route object for 2a0b:5d44::/30 with origin AS6761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6761 in the RIR database for the space. |
| ROA: none | 2a0b:5d46::/31 | No ROA covers it. Add a ROA for AS6761, maxLength 31. |
| Route object: none | 2a0b:5d46::/31 | No route object for it. A route object for 2a0b:5d44::/30 with origin AS6761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6761 in the RIR database for the space. |
| ROA: none | 94.77.64.0/18 | No ROA covers it. Add a ROA for AS6761, maxLength 18. |
| ROA: none | 94.77.64.0/19 | No ROA covers it. Add a ROA for AS6761, maxLength 19. |
| ROA: none | 94.77.96.0/19 | No ROA covers it. Add a ROA for AS6761, maxLength 19. |
| ROA: none | 185.210.240.0/23 | No ROA covers it. Add a ROA for AS6761, maxLength 23. |
| ROA: none | 185.210.240.0/24 | No ROA covers it. Add a ROA for AS6761, maxLength 24. |
| ROA: none | 185.210.241.0/24 | No ROA covers it. Add a ROA for AS6761, maxLength 24. |
| ROA: none | 185.210.242.0/23 | No ROA covers it. Add a ROA for AS6761, maxLength 23. |
| ROA: none | 185.210.243.0/24 | No ROA covers it. Add a ROA for AS6761, maxLength 24. |
Route objects not announced
Route objects with origin AS6761 whose prefix no peer sees AS6761 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.77.64.0/24 | RIPE | No ROA |
| 94.77.75.0/24 | RIPE | No ROA |
| 185.210.240.0/22 | RIPE | No ROA |
| 185.210.242.0/24 | RIPE | No ROA |
| 2a0b:5d40::/29 | RIPE | No ROA |
| 2a0b:5d40::/30 | RIPE | No ROA |
| 2a0b:5d44::/30 | RIPE | No ROA |
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.