Network · data from 2026-11-12
AS263329 FIBERCOM Telecomunicações
Registry name: AS263329 - FIBERCOM Telecomunicacoes, BR · PeeringDB
8IPv4 routes
87.5% RPKI valid · 87.5% with a route object
16IPv6 routes
100.0% RPKI valid · 43.8% with a route object
1RPKI invalid
1 origin · 0 maxLength
0No ROA
10 with no route object for this origin
17Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS263329, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS263329, 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.
| 187.63.151.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 2804:146c::/35 | Valid | Nonecovered by 2804:146c::/34 | 30 5%low visibility |
| 2804:146c:700::/40 | Valid | Nonecovered by 2804:146c::/34 | 30 5%low visibility |
| 2804:146c:2000::/35 | Valid | Nonecovered by 2804:146c::/34 | 30 5%low visibility |
| 2804:146c:4000::/35 | Valid | Nonecovered by 2804:146c:4000::/34 | 30 5%low visibility |
| 2804:146c:6000::/35 | Valid | Nonecovered by 2804:146c:4000::/34 | 30 5%low visibility |
| 2804:146c:8000::/35 | Valid | Nonecovered by 2804:146c:8000::/34 | 30 5%low visibility |
| 2804:146c:a000::/35 | Valid | Nonecovered by 2804:146c:8000::/34 | 30 5%low visibility |
| 2804:146c:c000::/35 | Valid | Nonecovered by 2804:146c:c000::/34 | 30 5%low visibility |
| 2804:146c:e000::/35 | Valid | Nonecovered by 2804:146c:c000::/34 | 30 5%low visibility |
| 191.7.188.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 191.7.188.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 191.7.190.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 2804:146c::/32 | Valid | Other IRR onlyTC | 636 100% |
| 2804:146c::/33 | Valid | Other IRR onlyTC | 636 100% |
| 2804:146c:8000::/33 | Valid | Other IRR onlyTC | 636 100% |
| 2804:146c:8000::/34 | Valid | Other IRR onlyTC | 635 100% |
| 2804:146c::/34 | Valid | Other IRR onlyTC | 30 5%low visibility |
| 2804:146c:4000::/34 | Valid | Other IRR onlyTC | 30 5%low visibility |
| 2804:146c:c000::/34 | Valid | Other IRR onlyTC | 30 5%low visibility |
| 191.7.188.0/24 | Valid | Other IRR onlyTC | 11 2%low visibility |
| 191.7.189.0/24 | Valid | Other IRR onlyTC | 11 2%low visibility |
| 191.7.190.0/24 | Valid | Other IRR onlyTC | 11 2%low visibility |
| 191.7.191.0/24 | Valid | Other IRR onlyTC | 11 2%low visibility |
AS-SET
PeeringDB's irr_as_set for AS263329: TC::AS263329:AS-FIBERCOM. 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 (AS263329 isn't in the set, or no route object for AS263329 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 | AS263329 in it | Not covered |
|---|---|---|---|---|---|
| TC::AS263329:AS-FIBERCOM | TC | 9 | 3 | 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 25 are in fix.csv.
- ROA: origin1
- Route object: none10
- Route object: RIR14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 187.63.151.0/24 | ROAs covering it name AS271455, not AS263329. If AS263329 should announce it, add a ROA for AS263329. |
| Route object: none | 187.63.151.0/24 | Route objects for it name AS271455. Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c::/35 | No route object for it. A route object for 2804:146c::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c:700::/40 | No route object for it. A route object for 2804:146c::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c:2000::/35 | No route object for it. A route object for 2804:146c::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c:4000::/35 | No route object for it. A route object for 2804:146c:4000::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c:6000::/35 | No route object for it. A route object for 2804:146c:4000::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c:8000::/35 | No route object for it. A route object for 2804:146c:8000::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c:a000::/35 | No route object for it. A route object for 2804:146c:8000::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c:c000::/35 | No route object for it. A route object for 2804:146c:c000::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: none | 2804:146c:e000::/35 | No route object for it. A route object for 2804:146c:c000::/34 with origin AS263329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263329 in the RIR database for the space. |
| Route object: RIR | 191.7.188.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.7.188.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.7.190.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:146c::/32 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:146c::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:146c:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:146c:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:146c::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:146c:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:146c:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.7.188.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.7.189.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.7.190.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.7.191.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS263329 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.