Network · data from 2026-11-12
AS264972 Livecom Serv e Com de Equipamentos de inf
Registry name: AS264972 - Livecom Serv e com de equipamentos de inf, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264972, 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.
| 2804:30c0:22::/48 | Valid | Nonecovered by 2804:30c0::/32 | 634 100% |
| 2804:30c0:23::/48 | Valid | Nonecovered by 2804:30c0::/32 | 634 100% |
| 2804:30c0:ffc0::/42 | Valid | Nonecovered by 2804:30c0::/32 | 631 99% |
| 170.247.183.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 170.0.128.0/22 | Valid | Other IRR onlyALTDB, RADB | 669 99% |
| 170.247.180.0/22 | Valid | Other IRR onlyALTDB, RADB | 669 99% |
| 170.0.128.0/23 | Valid | Other IRR onlyRADB | 667 99% |
| 170.0.130.0/23 | Valid | Other IRR onlyRADB | 667 99% |
| 170.247.180.0/23 | Valid | Other IRR onlyRADB | 667 99% |
| 170.247.182.0/23 | Valid | Other IRR onlyRADB | 666 99% |
| 2804:30c0::/32 | Valid | Other IRR onlyALTDB, RADB | 635 100% |
| 170.0.128.0/24 | Valid | Other IRR onlyRADB | 126 19% |
| 170.0.129.0/24 | Valid | Other IRR onlyRADB | 126 19% |
| 170.0.130.0/24 | Valid | Other IRR onlyRADB | 126 19% |
| 170.0.131.0/24 | Valid | Other IRR onlyRADB | 126 19% |
| 170.247.180.0/24 | Valid | Other IRR onlyRADB | 126 19% |
| 170.247.181.0/24 | Valid | Other IRR onlyRADB | 126 19% |
| 170.247.182.0/24 | Valid | Other IRR onlyRADB | 126 19% |
AS-SET
PeeringDB's irr_as_set for AS264972: AS-LIVECOM. 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 (AS264972 isn't in the set, or no route object for AS264972 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 | AS264972 in it | Not covered |
|---|---|---|---|---|---|
| AS-LIVECOM | RADB | 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 18 are in fix.csv.
- Route object: none3
- Route object: RIR15
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:30c0:22::/48 | No route object for it. A route object for 2804:30c0::/32 with origin AS264972 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264972 in the RIR database for the space. |
| Route object: none | 2804:30c0:23::/48 | No route object for it. A route object for 2804:30c0::/32 with origin AS264972 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264972 in the RIR database for the space. |
| Route object: none | 2804:30c0:ffc0::/42 | No route object for it. A route object for 2804:30c0::/32 with origin AS264972 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264972 in the RIR database for the space. |
| Route object: RIR | 170.247.183.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.0.128.0/22 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.247.180.0/22 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.0.128.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.0.130.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.247.180.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.247.182.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:30c0::/32 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.0.128.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.0.129.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.0.130.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.0.131.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.247.180.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.247.181.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.247.182.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264972 is announced.
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.