Network · data from 2026-11-12
AS11269 LinkBermuda
Registry name: LINKBERMUDA - LinkBermuda LTD, BM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11269, 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.
| 185.66.23.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 208.75.200.0/22 | No ROA | Other IRR onlyALTDB | 670 100% |
| 208.82.164.0/22 | No ROA | Other IRR onlyNTTCOM | 670 100% |
| 208.89.228.0/22 | No ROA | Other IRR onlyNTTCOM | 670 100% |
| 207.2.97.0/24 | Valid | Nonecovered by 207.2.96.0/21 | 670 100% |
| 207.2.98.0/24 | Valid | Nonecovered by 207.2.96.0/21 | 670 100% |
| 207.2.100.0/24 | Valid | Nonecovered by 207.2.96.0/21 | 670 100% |
| 207.2.101.0/24 | Valid | Nonecovered by 207.2.96.0/21 | 670 100% |
| 207.2.102.0/24 | Valid | Nonecovered by 207.2.96.0/21 | 670 100% |
| 207.2.103.0/24 | Valid | Nonecovered by 207.2.96.0/21 | 670 100% |
| 194.15.241.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 207.2.96.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 670 100% |
| 200.10.166.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 2605:e80::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 69.17.192.0/19 | Valid | RIR databaseARIN, RIPE-NONAUTH | 670 100% |
| 69.17.196.0/24 | Valid | RIR databaseARIN | 670 100% |
| 69.17.211.0/24 | Valid | RIR databaseARIN | 670 100% |
| 69.17.222.0/24 | Valid | RIR databaseARIN | 670 100% |
| 199.193.228.0/22 | Valid | RIR databaseARIN, NTTCOM | 670 100% |
| 200.1.160.0/24 | Valid | RIR databaseARIN | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS11269: AS-BERMUDA. 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 (AS11269 isn't in the set, or no route object for AS11269 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 | AS11269 in it | Not covered |
|---|---|---|---|---|---|
| AS-BERMUDA | RIPE | 13 | 1 | Yes | 0 |
| ARIN (also) | 15 | 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 22 are in fix.csv.
- ROA: none4
- Route object: none6
- Route object: RIR8
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.66.23.0/24 | No ROA covers it. Add a ROA for AS11269, maxLength 24. |
| Route object: RIR | 185.66.23.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.75.200.0/22 | No ROA covers it. Add a ROA for AS11269, maxLength 22. |
| Route object: RIR | 208.75.200.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 208.82.164.0/22 | No ROA covers it. Add a ROA for AS11269, maxLength 22. |
| Route object: RIR | 208.82.164.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 208.89.228.0/22 | No ROA covers it. Add a ROA for AS11269, maxLength 22. |
| Route object: RIR | 208.89.228.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: none | 207.2.97.0/24 | No route object for it. A route object for 207.2.96.0/21 with origin AS11269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11269 in the RIR database for the space. |
| Route object: none | 207.2.98.0/24 | No route object for it. A route object for 207.2.96.0/21 with origin AS11269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11269 in the RIR database for the space. |
| Route object: none | 207.2.100.0/24 | No route object for it. A route object for 207.2.96.0/21 with origin AS11269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11269 in the RIR database for the space. |
| Route object: none | 207.2.101.0/24 | No route object for it. A route object for 207.2.96.0/21 with origin AS11269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11269 in the RIR database for the space. |
| Route object: none | 207.2.102.0/24 | No route object for it. A route object for 207.2.96.0/21 with origin AS11269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11269 in the RIR database for the space. |
| Route object: none | 207.2.103.0/24 | No route object for it. A route object for 207.2.96.0/21 with origin AS11269 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11269 in the RIR database for the space. |
| Route object: RIR | 194.15.241.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 207.2.96.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 200.10.166.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2605:e80::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11269 whose prefix no peer sees AS11269 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.17.202.0/24 | ARIN | Valid |
| 69.17.210.0/24 | ARIN | Valid |
| 69.17.212.0/24 | ARIN | Valid |
| 207.2.96.0/21 | ARIN, RIPE-NONAUTH | Valid |
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.