Network · data from 2026-11-12
AS270013 INFOFRACTAL
Registry name: AS270013 - J AND J SPA (INFOFRACTAL), CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270013, 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.
| 200.14.81.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 151.242.242.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 2803:29e0::/32 | Valid | RIR databaseLACNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS270013: AS-INFOFRACTAL. 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 (AS270013 isn't in the set, or no route object for AS270013 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 | AS270013 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-INFOFRACTAL | In no IRR database read today. | |||||
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 3 are in fix.csv.
- AS-SET: not found1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: not found | AS-INFOFRACTAL | PeeringDB names AS-INFOFRACTAL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS270013 whose prefix no peer sees AS270013 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.73.159.0/24 | ARIN | Invalid: origin |
| 2a06:a006::/32 | RIPE | Invalid: origin |
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.