Network · data from 2026-11-12
AS12306 Plus.line AG
Registry name: PLUSLINE Plus.line AG, DE · PeeringDB
14IPv4 routes
92.9% RPKI valid · 35.7% with a route object
13IPv6 routes
92.3% RPKI valid · 38.5% with a route object
0RPKI invalid
0 origin · 0 maxLength
2No ROA
17 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
28Route objects not announced
registered with origin AS12306, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS12306, 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.
| 193.99.144.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a02:48e0::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 82.98.79.0/24 | Valid | Nonecovered by 82.98.64.0/18 | 672 100% |
| 82.98.88.0/24 | Valid | Nonecovered by 82.98.64.0/18 | 672 100% |
| 82.98.126.0/24 | Valid | Other origin onlycovered by 82.98.64.0/18 | 672 100% |
| 82.98.127.0/24 | Valid | Other origin onlycovered by 82.98.64.0/18 | 672 100% |
| 89.110.160.0/24 | Valid | Nonecovered by 89.110.128.0/18 | 672 100% |
| 89.110.176.0/24 | Valid | Nonecovered by 89.110.128.0/18 | 672 100% |
| 213.83.3.0/24 | Valid | Nonecovered by 213.83.0.0/18 | 672 100% |
| 213.83.10.0/24 | Valid | Nonecovered by 213.83.0.0/18 | 672 100% |
| 213.83.54.0/24 | Valid | Nonecovered by 213.83.0.0/18 | 672 100% |
| 2a02:2e0:3df::/48 | Valid | Nonecovered by 2a02:2e0::/29 | 636 100% |
| 2a02:2e0:3ef::/48 | Valid | Nonecovered by 2a02:2e0::/29 | 636 100% |
| 2a02:2e0:3f8::/48 | Valid | Nonecovered by 2a02:2e0::/29 | 636 100% |
| 2a02:2e0:3f9::/48 | Valid | Nonecovered by 2a02:2e0::/29 | 636 100% |
| 2a02:2e0:420::/48 | Valid | Nonecovered by 2a02:2e0::/29 | 636 100% |
| 2a02:2e0:cd4d::/48 | Valid | Other origin onlycovered by 2a02:2e0::/29 | 636 100% |
| 2a02:2e0:cd4e::/48 | Valid | Other origin onlycovered by 2a02:2e0::/29 | 636 100% |
| 2a05:c700:14::/48 | Valid | Nonecovered by 2a05:c700::/32 | 636 100% |
| 82.98.64.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 185.139.157.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.19.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 213.83.0.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 2a02:2e0:3fe::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0b:20c0:100::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a0b:20c0:6000::/36 | Valid | RIR databaseRIPE | 636 100% |
| 2a02:2e0::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS12306: AS-PLUSLINE. 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 (AS12306 isn't in the set, or no route object for AS12306 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 | AS12306 in it | Not covered |
|---|---|---|---|---|---|
| AS-PLUSLINE | RIPE | 45 | 11 | Yes | 0 |
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 47 are in fix.csv.
- ROA: none2
- Route object: none17
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.99.144.0/24 | No ROA covers it. Add a ROA for AS12306, maxLength 24. |
| ROA: none | 2a02:48e0::/48 | No ROA covers it. Add a ROA for AS12306, maxLength 48. |
| Route object: none | 82.98.79.0/24 | No route object for it. A route object for 82.98.64.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 82.98.88.0/24 | No route object for it. A route object for 82.98.64.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 82.98.126.0/24 | Route objects for it name AS206564. A route object for 82.98.64.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 82.98.127.0/24 | Route objects for it name AS206564. A route object for 82.98.64.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 89.110.160.0/24 | No route object for it. A route object for 89.110.128.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 89.110.176.0/24 | No route object for it. A route object for 89.110.128.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 213.83.3.0/24 | No route object for it. A route object for 213.83.0.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 213.83.10.0/24 | No route object for it. A route object for 213.83.0.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 213.83.54.0/24 | No route object for it. A route object for 213.83.0.0/18 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 2a02:2e0:3df::/48 | No route object for it. A route object for 2a02:2e0::/29 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 2a02:2e0:3ef::/48 | No route object for it. A route object for 2a02:2e0::/29 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 2a02:2e0:3f8::/48 | No route object for it. A route object for 2a02:2e0::/29 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 2a02:2e0:3f9::/48 | No route object for it. A route object for 2a02:2e0::/29 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 2a02:2e0:420::/48 | No route object for it. A route object for 2a02:2e0::/29 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 2a02:2e0:cd4d::/48 | Route objects for it name AS206564. A route object for 2a02:2e0::/29 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 2a02:2e0:cd4e::/48 | Route objects for it name AS206564. A route object for 2a02:2e0::/29 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
| Route object: none | 2a05:c700:14::/48 | No route object for it. A route object for 2a05:c700::/32 with origin AS12306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12306 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12306 whose prefix no peer sees AS12306 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.98.67.0/24 | RIPE | Valid |
| 82.98.78.0/24 | RIPE | Valid |
| 82.98.80.0/24 | RIPE | Valid |
| 82.98.90.0/24 | RIPE | Valid |
| 82.98.91.0/24 | RIPE | Valid |
| 82.98.93.0/24 | RIPE | Valid |
| 89.110.128.0/18 | RIPE | Valid |
| 185.7.71.0/24 | RIPE | Valid |
| 185.59.248.0/24 | RIPE | Invalid: origin |
| 185.59.249.0/24 | RIPE | Invalid: origin |
| 185.59.250.0/24 | RIPE | Invalid: origin |
| 185.59.251.0/24 | RIPE | Invalid: origin |
| 193.202.119.0/24 | RIPE | Valid |
| 194.56.221.0/24 | RIPE | Valid |
| 212.19.40.0/24 | RIPE | Valid |
| 212.19.48.0/24 | RIPE | Valid |
| 212.19.61.0/24 | RIPE | Valid |
| 213.83.31.0/24 | RIPE | Valid |
| 213.83.48.0/24 | RIPE | Valid |
| 2001:67c:b24::/48 | RIPE | Invalid: origin |
| 2a02:2e0:1::/48 | RIPE | Valid |
| 2a02:2e0:a::/48 | RIPE | Valid |
| 2a02:2e0:a:b::/64 | RIPE | Valid |
| 2a02:2e0:3e8::/48 | RIPE | Valid |
| 2a02:2e0:3f5::/48 | RIPE | Valid |
| 2a02:2e0:fffe::/48 | RIPE | Valid |
| 2a02:7060::/32 | RIPE | No ROA |
| 2a05:c700::/32 | 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.