Network · data from 2026-11-12
AS30931 IG Index PLC
Registry name: IGINDEX-PLC IG Index Ltd., GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30931, 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.
| 2a0c:c900::/48 | Valid | Nonecovered by 2a0c:c900::/29 | 634 100% |
| 2a0c:c900:1::/48 | Valid | Nonecovered by 2a0c:c900::/29 | 634 100% |
| 2a0c:c900:2::/48 | Valid | Nonecovered by 2a0c:c900::/29 | 634 100% |
| 91.223.203.0/24 | Valid | RIR databaseNTTCOM, RADB, REACH, RIPE | 672 100% |
| 91.223.218.0/24 | Valid | RIR databaseNTTCOM, RADB, REACH, RIPE | 672 100% |
| 185.109.140.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.109.141.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.233.4.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.233.6.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.30.41.0/24 | Valid | RIR databaseNTTCOM, RADB, REACH, RIPE | 672 100% |
| 194.107.118.0/24 | Valid | RIR databaseNTTCOM, RADB, REACH, RIPE | 672 100% |
| 195.234.39.0/24 | Valid | RIR databaseNTTCOM, RADB, REACH, RIPE | 672 100% |
| 185.109.140.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.109.140.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.109.142.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.109.143.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.233.4.0/22 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 2001:67c:1b24::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:c900::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS30931: AS-IG. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS30931 isn't in the set, or no route object for AS30931 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS30931 in it | Not covered |
|---|---|---|---|---|---|
| AS-IG | RIPE | 1 | 1 | Yes | 0 |
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 4 are in fix.csv.
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a0c:c900::/48 | No route object for it. A route object for 2a0c:c900::/29 with origin AS30931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30931 in the RIR database for the space. |
| Route object: none | 2a0c:c900:1::/48 | No route object for it. A route object for 2a0c:c900::/29 with origin AS30931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30931 in the RIR database for the space. |
| Route object: none | 2a0c:c900:2::/48 | No route object for it. A route object for 2a0c:c900::/29 with origin AS30931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30931 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS30931 whose prefix no peer sees AS30931 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.109.142.0/23 | 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.