bgpreport

Network · data from 2026-11-12

AS27552 TWDX IP

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

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

Announced routes

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

162.223.52.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 67
198.203.31.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 67
205.201.60.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 67
2001:4830:c200::/48 Valid Nonecovered by 2001:4830:c000::/36 636 100% 67
208.118.224.0/20 Valid Other IRR onlyALTDB, RIPE-NONAUTH 673 100% 67
216.93.240.0/20 Valid Other IRR onlyALTDB, RIPE-NONAUTH 673 100% 67
198.160.60.0/23 Valid Other IRR onlyALTDB, RIPE-NONAUTH 671 100% 67
198.160.62.0/23 Valid Other IRR onlyALTDB, RIPE-NONAUTH 671 100% 67
199.114.248.0/22 Valid Other IRR onlyALTDB, RIPE-NONAUTH 671 100% 67
2001:4830:100::/40 Valid Other IRR onlyALTDB, RIPE-NONAUTH 636 100% 67
2001:4830:c000::/36 Valid Other IRR onlyALTDB, RIPE-NONAUTH 636 100% 67
162.219.96.0/24 Valid Other IRR onlyRIPE-NONAUTH 188 28% 56
69.72.24.0/22 Valid RIR databaseALTDB, ARIN, RADB 671 100% 67
185.134.180.0/22 Valid RIR databaseALTDB, RIPE 671 100% 67
198.203.30.0/24 Valid RIR databaseALTDB, ARIN, RADB 671 100% 67
2a06:ee01::/32 Valid RIR databaseALTDB, RADB, RIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS27552: AS-TOWARDEX. 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 (AS27552 isn't in the set, or no route object for AS27552 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 objectsAS27552 in itNot covered
AS-TOWARDEX RADB 3924910,768 Yes 0
ALTDB (also)8 member sets in no database: AS-CORESITE, AS-CPUL, AS-ERC-BROADBAND, AS-ROUTED, AS-SHRE … 244206,990 Yes 0
RIPE (also)13 member sets in no database: AS-CAMBANDCONS, AS-CELT, AS-CORESITE, AS-CPUL, AS-ENDOFFICE … 116131,132 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 27 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR11
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none162.223.52.0/22No ROA covers it. Add a ROA for AS27552, maxLength 22.671 of 673
Route object: RIR162.223.52.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.203.31.0/24No ROA covers it. Add a ROA for AS27552, maxLength 24.671 of 673
Route object: RIR198.203.31.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none205.201.60.0/24No ROA covers it. Add a ROA for AS27552, maxLength 24.671 of 673
Route object: RIR205.201.60.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: none2001:4830:c200::/48No route object for it. A route object for 2001:4830:c000::/36 with origin AS27552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27552 in the RIR database for the space.636 of 636
Route object: RIR208.118.224.0/20Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR216.93.240.0/20Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR198.160.60.0/23Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR198.160.62.0/23Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR199.114.248.0/22Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR2001:4830:100::/40Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.636 of 636
Route object: RIR2001:4830:c000::/36Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.636 of 636
Route object: RIR162.219.96.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.188 of 673

Route objects not announced

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

100.42.124.0/23ALTDBNo ROA
192.88.99.0/24ALTDBNo ROA
208.70.208.0/22ALTDB, RADBNo ROA
208.118.224.0/21ALTDBValid
208.118.232.0/21ALTDBValid
216.93.240.0/21ALTDBValid
216.93.240.0/24ALTDBValid
216.93.242.0/24ALTDBValid
216.93.248.0/21ALTDBValid
216.93.251.0/24ALTDBValid
2001:1868:53::/48ALTDBInvalid: origin
2001:4830:200::/40ALTDBValid

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.