Network · data from 2026-11-12
AS201949 Seed Technologies
Registry name: SEEDTECHNOLOGIES Seed Technologies LTD., GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201949, 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.
| 2a12:5343:6::/48 | Invalid: origin | None | 23 4%low visibility |
| 91.221.116.0/24 | Invalid: origin | Other origin only | 5 1%low visibility |
| 95.170.20.0/24 | Invalid: origin | Other origin only | 5 1%low visibility |
| 89.117.222.0/24 | No ROA | Other origin only | 8 1%low visibility |
| 2a0c:9a40:86c0::/48 | Valid | Nonecovered by 2a0c:9a40:86c0::/44 | 636 100% |
| 87.229.100.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 45.88.8.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a0c:9a40:86cf::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS201949: AS201949:AS-SET. 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 (AS201949 isn't in the set, or no route object for AS201949 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 | AS201949 in it | Not covered |
|---|---|---|---|---|---|
| AS201949:AS-SET | RIPE | 1 | 1 | Yes | 4 |
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: origin3
- ROA: none1
- Route object: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a12:5343:6::/48 | ROAs covering it name AS16509, not AS201949. If AS201949 should announce it, add a ROA for AS201949. |
| Route object: none | 2a12:5343:6::/48 | No route object for it. Add a route object with origin AS201949 in the RIR database for the space. |
| ROA: origin | 91.221.116.0/24 | ROAs covering it name AS2856, not AS201949. If AS201949 should announce it, add a ROA for AS201949. |
| Route object: none | 91.221.116.0/24 | Route objects for it name AS2856. Add a route object with origin AS201949 in the RIR database for the space. |
| ROA: origin | 95.170.20.0/24 | ROAs covering it name AS834, not AS201949. If AS201949 should announce it, add a ROA for AS201949. |
| Route object: none | 95.170.20.0/24 | Route objects for it name AS834. Add a route object with origin AS201949 in the RIR database for the space. |
| ROA: none | 89.117.222.0/24 | No ROA covers it. Add a ROA for AS201949, maxLength 24. |
| Route object: none | 89.117.222.0/24 | Route objects for it name AS834. Add a route object with origin AS201949 in the RIR database for the space. |
| Route object: none | 2a0c:9a40:86c0::/48 | No route object for it. A route object for 2a0c:9a40:86c0::/44 with origin AS201949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201949 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201949 whose prefix no peer sees AS201949 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0c:9a40:86c0::/44 | 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.