Network · data from 2026-11-12
AS208483 WERIDATA-LLC WERIDATA LLC
Registry name: WERIDATA-LLC WERIDATA LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208483, 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.
| 45.8.196.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
AS-SET
AS208483 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 12 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.8.196.0/24 | ROAs covering it name AS834, not AS208483. If AS208483 should announce it, add a ROA for AS208483. |
| Route object: none | 45.8.196.0/24 | Route objects for it name AS834. Add a route object with origin AS208483 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS208483 whose prefix no peer sees AS208483 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.57.135.0/24 | RADB, RIPE | Valid |
| 45.74.176.0/24 | RIPE | Valid |
| 45.155.159.0/24 | RADB, RIPE | Valid |
| 45.158.57.0/24 | RADB, RIPE | Valid |
| 82.129.4.0/24 | RIPE | No ROA |
| 91.198.66.0/24 | RADB, RIPE | Valid |
| 141.11.65.0/24 | RADB, RIPE | Valid |
| 193.160.222.0/24 | RADB, RIPE | Valid |
| 213.254.170.0/24 | RADB, RIPE | Valid |
| 2a13:9500:99::/48 | RIPE | 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.