bgpreport

Network · data from 2026-11-12

AS22188 Solantic

Registry name: SOLANTIC - Solantic Corporation, US · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 50.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 AS22188, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22188, 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.
2604:bc40:300::/48 Valid Nonecovered by 2604:bc40::/32 629 99% 67
23.134.96.0/23 Valid RIR databaseARIN 671 100% 67
23.134.96.0/24 Valid RIR databaseARIN 671 100% 67
168.151.10.0/24 Valid RIR databaseARIN 671 100% 67
23.134.97.0/24 Valid RIR databaseARIN 664 99% 67
2604:bc40::/32 Valid RIR databaseARIN 605 95% 67

AS-SET

PeeringDB's irr_as_set for AS22188: AS22188. 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 (AS22188 isn't in the set, or no route object for AS22188 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 objectsAS22188 in itNot covered
AS22188 A single AS number, not a set: AS22188 (this network), 5 route objects.

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: none2604:bc40:300::/48No route object for it. A route object for 2604:bc40::/32 with origin AS22188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22188 in the RIR database for the space.629 of 636

Route objects not announced

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