bgpreport

Network · data from 2026-11-12

AS25787 Rowe Wireless Networks

Registry name: ROWE-NETWORKS - Rowe Wireless Networks LLC, US · PeeringDB

7IPv4 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
0Low visibility seen by under 10% of full-table peers
33Route objects not announced registered with origin AS25787, seen from no peer

Announced routes

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

2606:1640::/32 Valid RIR databaseARIN 635 100% 69
162.217.20.0/22 Valid RIR databaseARIN, RADB 607 90% 68
205.137.252.0/22 Valid RIR databaseARIN, RADB 607 90% 68
74.123.208.0/24 Valid RIR databaseARIN 605 90% 68
142.249.140.0/22 Valid RIR databaseARIN 604 90% 68
142.249.140.0/24 Valid RIR databaseARIN 598 89% 68
142.249.141.0/24 Valid RIR databaseARIN 598 89% 68
142.249.142.0/24 Valid RIR databaseARIN 598 89% 68

AS-SET

PeeringDB's irr_as_set for AS25787: AS-ROWE-INTERNET. 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 (AS25787 isn't in the set, or no route object for AS25787 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 objectsAS25787 in itNot covered
AS-ROWE-INTERNET ARIN 32128 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 33 are in fix.csv.

  • Route object: not announced33

Route objects not announced

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

23.152.144.0/24ARINInvalid: origin
23.152.145.0/24ARINInvalid: origin
74.123.208.0/21ARINValid
74.123.209.0/24ARINValid
74.123.210.0/24ARINValid
74.123.211.0/24ARINValid
74.123.212.0/24ARINValid
74.123.213.0/24ARIN, RADBValid
74.123.214.0/24ARIN, RADBValid
74.123.215.0/24ARINValid
142.249.143.0/24ARINValid
162.217.20.0/24ARINValid
162.217.21.0/24ARINValid
162.217.22.0/24ARINValid
162.217.23.0/24ARINValid
205.137.252.0/24ARINValid
205.137.253.0/24ARINValid
205.137.254.0/24ARINValid
205.137.255.0/24ARINValid
207.90.216.0/22ARIN, RADBValid
207.90.216.0/24ARINValid
207.90.217.0/24ARINValid
207.90.218.0/24ARINValid
207.90.219.0/24ARINValid
208.78.200.0/21ARINValid
208.78.200.0/24ARINValid
208.78.201.0/24ARINValid
208.78.202.0/24ARINValid
208.78.203.0/24ARINValid
208.78.204.0/24ARINValid
208.78.205.0/24ARINValid
208.78.206.0/24ARINValid
208.78.207.0/24ARINValid

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.