bgpreport

Network · data from 2026-11-12

AS25623 CISN2 Enterprise Communications

Registry name: CISN2 - TowardEX Technologies International, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25623, 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.
2001:4830:3100::/48 Valid None 636 100% 67
2a06:ee05::/32 Valid Other origin only 636 100% 67
8.20.191.0/24 Valid Other IRR onlyALTDB, RIPE-NONAUTH 671 100% 67
162.219.97.0/24 Valid Other IRR onlyALTDB, RIPE-NONAUTH 671 100% 67
199.114.249.0/24 Valid Other IRR onlyALTDB, RIPE-NONAUTH 671 100% 67
199.114.251.0/24 Valid Other IRR onlyRIPE-NONAUTH 671 100% 67
2001:4830:200::/40 Valid Other IRR onlyRIPE-NONAUTH 636 100% 67
2001:4830:2070::/48 Valid Other IRR onlyALTDB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS25623: AS-CISN2. 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 (AS25623 isn't in the set, or no route object for AS25623 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 objectsAS25623 in itNot covered
AS-CISN2 RIPE 116 Yes 2
ALTDB (also) 116 Yes 2

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

  • Route object: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none2001:4830:3100::/48No route object for it. Add a route object with origin AS25623 in the RIR database for the space.636 of 636
Route object: none2a06:ee05::/32Route objects for it name AS22147. Add a route object with origin AS25623 in the RIR database for the space.636 of 636
Route object: RIR8.20.191.0/24Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR162.219.97.0/24Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR199.114.249.0/24Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR199.114.251.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR2001:4830:200::/40Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.636 of 636
Route object: RIR2001:4830:2070::/48Route object only in ALTDB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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