Network · data from 2026-11-12
AS263944 FiberNet Telecomunicacoes
Registry name: AS263944 - FiberNet Telecomunicacoes, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263944, 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:2828::/32 | No ROA | Other IRR onlyRADB, TC | 634 100% |
| 138.219.110.0/23 | Valid | Nonecovered by 138.219.108.0/22 | 670 100% |
| 138.219.108.0/23 | Valid | Nonecovered by 138.219.108.0/22 | 669 99% |
| 138.219.108.0/22 | Valid | Other IRR onlyRADB, TC | 670 100% |
AS-SET
AS263944's PeeringDB record names no AS-SET.
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 5 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:2828::/32 | No ROA covers it. Add a ROA for AS263944, maxLength 32. |
| Route object: RIR | 2804:2828::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: none | 138.219.110.0/23 | No route object for it. A route object for 138.219.108.0/22 with origin AS263944 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263944 in the RIR database for the space. |
| Route object: none | 138.219.108.0/23 | No route object for it. A route object for 138.219.108.0/22 with origin AS263944 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263944 in the RIR database for the space. |
| Route object: RIR | 138.219.108.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS263944 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.