Network · data from 2026-11-12
AS26949 Harbor Communications
Registry name: HARBOR-COMMUNICATIONS-LLC - Harbor Communications, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26949, 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.
| 64.28.56.0/22 | No ROA | Nonecovered by 64.28.48.0/20 | 672 100% |
| 64.28.58.0/24 | No ROA | Nonecovered by 64.28.48.0/20 | 672 100% |
| 69.57.50.0/24 | No ROA | Nonecovered by 69.57.48.0/20 | 672 100% |
| 2607:f9c8::/32 | No ROA | RIR databaseARIN | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS26949: AS-HARBORCOM. 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 (AS26949 isn't in the set, or no route object for AS26949 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 | AS26949 in it | Not covered |
|---|---|---|---|---|---|
| AS-HARBORCOM | ARIN1 member set in no database: AS-HARBORCOM-C | 1 | 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 10 are in fix.csv.
- ROA: none4
- Route object: none3
- AS-SET: missing member1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.28.56.0/22 | No ROA covers it. Add a ROA for AS26949, maxLength 22. |
| Route object: none | 64.28.56.0/22 | No route object for it. A route object for 64.28.48.0/20 with origin AS26949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26949 in the RIR database for the space. |
| ROA: none | 64.28.58.0/24 | No ROA covers it. Add a ROA for AS26949, maxLength 24. |
| Route object: none | 64.28.58.0/24 | No route object for it. A route object for 64.28.48.0/20 with origin AS26949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26949 in the RIR database for the space. |
| ROA: none | 69.57.50.0/24 | No ROA covers it. Add a ROA for AS26949, maxLength 24. |
| Route object: none | 69.57.50.0/24 | No route object for it. A route object for 69.57.48.0/20 with origin AS26949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26949 in the RIR database for the space. |
| ROA: none | 2607:f9c8::/32 | No ROA covers it. Add a ROA for AS26949, maxLength 32. |
| AS-SET: missing member | AS-HARBORCOM | AS-HARBORCOM (ARIN) lists AS-HARBORCOM-C; no IRR database read has it. |
Route objects not announced
Route objects with origin AS26949 whose prefix no peer sees AS26949 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.28.48.0/20 | ALTDB | No ROA |
| 69.57.48.0/20 | ALTDB | 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.