bgpreport

Network · data from 2026-11-12

AS1448 United Cooperative Services

Registry name: UNITED-BROADBAND - United Cooperative Services, US · PeeringDB

12IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS1448, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS1448, 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.

156.146.128.0/17 Valid RIR databaseARIN 673 100% 67
156.146.128.0/18 Valid RIR databaseARIN 673 100% 67
156.146.208.0/20 Valid RIR databaseARIN 673 100% 67
158.41.128.0/17 Valid RIR databaseARIN 673 100% 67
158.41.128.0/19 Valid RIR databaseARIN 673 100% 67
158.41.160.0/20 Valid RIR databaseARIN 673 100% 67
158.41.176.0/21 Valid RIR databaseARIN 673 100% 67
158.41.208.0/20 Valid RIR databaseARIN 673 100% 67
158.41.240.0/20 Valid RIR databaseARIN 673 100% 67
158.51.140.0/22 Valid RIR databaseARIN 671 100% 67
2605:9840::/32 Valid RIR databaseARIN 636 100% 67
156.146.192.0/20 Valid RIR databaseARIN 2 0%low visibility 2
156.146.224.0/19 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS1448: ARIN::AS-UECS. 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 (AS1448 isn't in the set, or no route object for AS1448 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.

NameDatabaseASNsSets Route objectsAS1448 in itNot covered
ARIN::AS-UECS ARIN 1117 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 4 are in fix.csv.

  • Route object: not announced4

Route objects not announced

Route objects with origin AS1448 whose prefix no peer sees AS1448 announce. Many are kept on purpose (backup routes, space announced only in some places).

134.82.0.0/19ARINValid
158.41.184.0/21ARINValid
158.41.192.0/20ARINValid
158.41.224.0/20ARINValid

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.