Network · data from 2026-11-12
AS199129 Direct Connect
Registry name: DIRECTCONNECT-AS Direct Connect (ISP) Ltd, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199129, 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.
| 82.39.205.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 82.108.133.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 2a13:9500:1b5::/48 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS199129: AS199129. 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 (AS199129 isn't in the set, or no route object for AS199129 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.
| Name | Database | ASNs | Sets | AS199129 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS199129 | A single AS number, not a set: AS199129 (this network), 1 route objects. | |||||
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 4 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 82.39.205.0/24 | ROAs covering it name AS834, not AS199129. If AS199129 should announce it, add a ROA for AS199129. |
| Route object: none | 82.39.205.0/24 | Route objects for it name AS834. Add a route object with origin AS199129 in the RIR database for the space. |
| ROA: none | 82.108.133.0/24 | No ROA covers it. Add a ROA for AS199129, maxLength 24. |
| Route object: none | 82.108.133.0/24 | Route objects for it name AS834. Add a route object with origin AS199129 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS199129 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.