bgpreport

Network · data from 2026-11-12

AS33548 Unwired Broadband

Registry name: UNWIRED-NOC - Unwired Broadband, LLC, US · PeeringDB

20IPv4 routes 100.0% RPKI valid · 95.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 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS33548, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33548, 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.
142.214.231.0/24 Valid None 670 100% 67
23.227.96.0/19 Valid RIR databaseARIN 672 100% 67
64.192.0.0/21 Valid RIR databaseARIN 672 100% 67
64.203.112.0/20 Valid RIR databaseARIN 672 100% 67
67.204.32.0/19 Valid RIR databaseARIN 672 100% 67
104.200.32.0/20 Valid RIR databaseARIN 672 100% 67
104.247.128.0/20 Valid RIR databaseARIN 672 100% 67
104.247.144.0/21 Valid RIR databaseARIN 672 100% 67
195.155.0.0/18 Valid RIR databaseARIN 672 100% 67
198.210.32.0/19 Valid RIR databaseARIN 672 100% 67
205.157.144.0/20 Valid RIR databaseARIN 672 100% 67
206.162.224.0/20 Valid RIR databaseARIN 672 100% 67
209.54.32.0/20 Valid RIR databaseARIN 672 100% 67
64.193.92.0/22 Valid RIR databaseARIN 670 100% 67
64.194.132.0/22 Valid RIR databaseARIN 670 100% 67
104.254.100.0/22 Valid RIR databaseARIN 670 100% 67
142.214.229.0/24 Valid RIR databaseARIN 670 100% 67
162.251.200.0/22 Valid RIR databaseARIN 670 100% 67
192.102.139.0/24 Valid RIR databaseARIN, RADB 669 99% 67
207.177.128.0/18 Valid RIR databaseARIN 669 99% 67
2606:6e80::/28 Valid RIR databaseARIN 635 100% 68

AS-SET

PeeringDB's irr_as_set for AS33548: AS33548:AS-UNWIRED. 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 (AS33548 isn't in the set, or no route object for AS33548 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 objectsAS33548 in itNot covered
AS33548:AS-UNWIRED ARIN 6237 Yes 1

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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none142.214.231.0/24No route object for it. Add a route object with origin AS33548 in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS33548 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.