Network · data from 2026-11-12
AS269266 FIBER LINK NETWORK TECNOLOGIA EM COMUNICACOES
Registry name: AS269266 - FIBERLINK NETWORK, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269266, 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:61f0::/42 | No ROA | Nonecovered by 2804:61f0::/32 | 636 100% |
| 45.182.42.0/24 | No ROA | Other IRR onlyALTDB, RADB | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS269266: AS-269266. 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 (AS269266 isn't in the set, or no route object for AS269266 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 | AS269266 in it | Not covered |
|---|---|---|---|---|---|
| AS-269266 | ALTDB | 69 | 2 | 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 15 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:61f0::/42 | No ROA covers it. Add a ROA for AS269266, maxLength 42. |
| Route object: none | 2804:61f0::/42 | No route object for it. A route object for 2804:61f0::/32 with origin AS269266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269266 in the RIR database for the space. |
| ROA: none | 45.182.42.0/24 | No ROA covers it. Add a ROA for AS269266, maxLength 24. |
| Route object: RIR | 45.182.42.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269266 whose prefix no peer sees AS269266 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:61f0::/32 | ALTDB, RADB | No ROA |
| 2804:61f0:1::/48 | RADB | No ROA |
| 2804:61f0:2::/48 | RADB | No ROA |
| 2804:61f0:3::/48 | RADB | No ROA |
| 2804:61f0:4::/48 | RADB | No ROA |
| 2804:61f0:6::/48 | RADB | No ROA |
| 2804:61f0:7::/48 | RADB | No ROA |
| 2804:61f0:d::/48 | RADB | No ROA |
| 2804:61f0:10::/48 | RADB | No ROA |
| 2804:61f0:12::/48 | RADB | No ROA |
| 2804:61f0:18::/45 | RADB | No ROA |
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.