Network · data from 2026-11-12
AS265684 Infinitum
Registry name: AS265684 - INFINITUM S.A., GT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265684, 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.
| 2803:ac30::/32 | No ROA | None | 636 100% |
| 2803:d20::/32 | Valid | Other IRR onlyRADB | 634 100% |
| 2803:e1c0::/32 | Valid | RIR databaseLACNIC, RADB | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS265684: AS265684:AS-PEERS. 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 (AS265684 isn't in the set, or no route object for AS265684 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 | AS265684 in it | Not covered |
|---|---|---|---|---|---|
| AS265684:AS-PEERS | LACNIC | 2 | 1 | No | 3 |
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 18 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR1
- AS-SET: own ASN1
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2803:ac30::/32 | No ROA covers it. Add a ROA for AS265684, maxLength 32. |
| Route object: none | 2803:ac30::/32 | No route object for it. Add a route object with origin AS265684 in the RIR database for the space. |
| Route object: RIR | 2803:d20::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS265684:AS-PEERS | AS265684 isn't in AS265684:AS-PEERS (LACNIC) once expanded. Add AS265684 to it. |
Route objects not announced
Route objects with origin AS265684 whose prefix no peer sees AS265684 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.5.116.0/24 | LACNIC | Valid |
| 45.5.117.0/24 | LACNIC | Valid |
| 45.5.118.0/24 | LACNIC | Valid |
| 45.5.119.0/24 | LACNIC | Valid |
| 45.186.104.0/24 | LACNIC | Valid |
| 45.186.105.0/24 | LACNIC | Valid |
| 45.186.106.0/24 | LACNIC | Valid |
| 45.186.107.0/24 | LACNIC | Valid |
| 45.226.176.0/24 | LACNIC | Valid |
| 45.228.232.0/22 | RADB | No ROA |
| 45.228.233.0/24 | LACNIC, RADB | Valid |
| 45.228.234.0/24 | LACNIC | Valid |
| 45.228.235.0/24 | LACNIC | Valid |
| 2803:9760::/32 | RADB | 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.