Network · data from 2026-11-12
AS264930 Conecta Fibra
Registry name: AS264930 - Conecta UP, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264930, 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.
| 168.228.214.0/23 | Valid | Nonecovered by 168.228.212.0/22 | 670 100% |
| 168.228.212.0/23 | Valid | Nonecovered by 168.228.212.0/22 | 667 99% |
| 2804:301c:10::/48 | Valid | Nonecovered by 2804:301c::/32 | 631 99% |
| 168.228.215.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 168.228.212.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 168.228.212.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 168.228.213.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 168.228.214.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 2804:301c::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 631 99% |
| 2804:301c:2::/48 | Valid | Other IRR onlyTC | 631 99% |
| 2804:301c:4::/48 | Valid | Other IRR onlyTC | 630 99% |
AS-SET
PeeringDB's irr_as_set for AS264930: AS264930. 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 (AS264930 isn't in the set, or no route object for AS264930 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 | AS264930 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS264930 | A single AS number, not a set: AS264930 (this network), 8 route objects. | |||||
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 11 are in fix.csv.
- Route object: none3
- Route object: RIR8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 168.228.214.0/23 | No route object for it. A route object for 168.228.212.0/22 with origin AS264930 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264930 in the RIR database for the space. |
| Route object: none | 168.228.212.0/23 | No route object for it. A route object for 168.228.212.0/22 with origin AS264930 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264930 in the RIR database for the space. |
| Route object: none | 2804:301c:10::/48 | No route object for it. A route object for 2804:301c::/32 with origin AS264930 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264930 in the RIR database for the space. |
| Route object: RIR | 168.228.215.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.212.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.212.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.213.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.214.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:301c::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:301c:2::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:301c:4::/48 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264930 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.