bgpreport

Network · data from 2026-11-12

AS8232 GXS-EUROPE GXS International Inc.

Registry name: GXS-EUROPE GXS International Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8232, 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.
149.235.32.0/23 No ROA Other origin only 673 100% 67
149.235.34.0/23 No ROA Other origin only 673 100% 67

AS-SET

AS8232 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none2
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none149.235.32.0/23No ROA covers it. Add a ROA for AS8232, maxLength 23.673 of 673
Route object: none149.235.32.0/23Route objects for it name AS203160. Add a route object with origin AS8232 in the RIR database for the space.673 of 673
ROA: none149.235.34.0/23No ROA covers it. Add a ROA for AS8232, maxLength 23.673 of 673
Route object: none149.235.34.0/23Route objects for it name AS203160. Add a route object with origin AS8232 in the RIR database for the space.673 of 673

Route objects not announced

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

149.235.8.0/21RADBNo ROA
149.235.8.0/24RADBNo ROA
149.235.40.0/21RADBNo ROA
150.105.120.0/21RADBNo ROA
204.90.181.0/24RIPE-NONAUTHNo ROA
204.90.182.0/24RIPE-NONAUTHNo ROA

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.