Network · data from 2026-11-12
AS42615 igloo22225 - AS42615
Registry name: igloo22225 June Slater, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42615, 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:6b86:1200::/39 | No ROA | None | 1 0%low visibility |
| 44.2.18.0/24 | No ROA | Other IRR onlyALTDB, RADB | 671 100% |
| 44.31.118.0/24 | No ROA | Other IRR onlyALTDB, RADB | 671 100% |
| 185.186.11.0/24 | Valid | RIR databaseALTDB, RIPE | 673 100% |
| 23.132.96.0/24 | Valid | RIR databaseALTDB, ARIN | 671 100% |
| 2602:fafb::/36 | Valid | RIR databaseALTDB, ARIN | 635 100% |
| 2a0b:6b81:4::/48 | Valid | RIR databaseALTDB, RIPE | 635 100% |
| 2a0b:6b81:403::/48 | Valid | RIR databaseALTDB, RIPE | 635 100% |
| 2a0b:6b81:401::/48 | Valid | RIR databaseALTDB, RIPE | 634 100% |
| 2a0b:6b87::/32 | Valid | RIR databaseALTDB, RADB, RIPE | 634 100% |
| 2a0b:6b81:3::/48 | Valid | RIR databaseALTDB, RIPE | 633 100% |
| 2a0b:6b86:1300::/40 | Valid | RIR databaseALTDB, RIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS42615: AS-IGLOO22225. 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 (AS42615 isn't in the set, or no route object for AS42615 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 | AS42615 in it | Not covered |
|---|---|---|---|---|---|
| AS-IGLOO22225 | RIPE | 16 | 3 | Yes | 1 |
| ALTDB (also)2 member sets in no database: AS-APERTURE-NETWORKS, AS-BASIL | 10 | 1 | Yes | 1 | |
| ARIN (also)2 member sets in no database: AS-APERTURE-NETWORKS, AS-BASIL | 10 | 1 | Yes | 1 |
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 8 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0b:6b86:1200::/39 | No ROA covers it. Add a ROA for AS42615, maxLength 39. |
| Route object: none | 2a0b:6b86:1200::/39 | No route object for it. Add a route object with origin AS42615 in the RIR database for the space. |
| ROA: none | 44.2.18.0/24 | No ROA covers it. Add a ROA for AS42615, maxLength 24. |
| Route object: RIR | 44.2.18.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 44.31.118.0/24 | No ROA covers it. Add a ROA for AS42615, maxLength 24. |
| Route object: RIR | 44.31.118.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42615 whose prefix no peer sees AS42615 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.142.88.0/24 | ARIN | Valid |
| 44.48.41.0/24 | ALTDB | 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.