Network · data from 2026-11-12
AS32627 BIDS-TRADING - BIDS Trading L.P.
Registry name: BIDS-TRADING - BIDS Trading L.P., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS32627, 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.
| 173.241.92.0/24 | Valid | None | 655 97% |
AS-SET
AS32627 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 5 are in fix.csv.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 173.241.92.0/24 | No route object for it. Add a route object with origin AS32627 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS32627 whose prefix no peer sees AS32627 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.199.142.0/24 | ALTDB, RADB | No ROA |
| 173.241.87.0/24 | RADB | Valid |
| 173.241.89.0/24 | RADB | Valid |
| 173.241.90.0/24 | RADB | Valid |
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.