Network · data from 2026-11-12
AS24685 DOMONET Load.me sp. z o. o.
Registry name: DOMONET Load.me sp. z o. o., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24685, 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.
| 212.110.139.0/24 | Invalid: origin | None | 9 1%low visibility |
| 80.92.233.0/24 | Valid | Other origin only | 672 100% |
| 80.92.234.0/24 | Valid | Other origin only | 672 100% |
| 128.0.172.0/24 | Valid | None | 672 100% |
| 194.28.198.0/24 | Valid | None | 10 1%low visibility |
| 85.90.211.48/32 | Valid | Nonecovered by 85.90.211.0/24 | 3 0%low visibility |
| 85.90.211.217/32 | Valid | Nonecovered by 85.90.211.0/24 | 3 0%low visibility |
| 85.90.211.221/32 | Valid | Nonecovered by 85.90.211.0/24 | 3 0%low visibility |
| 92.60.179.130/32 | Valid | Nonecovered by 92.60.179.0/24 | 3 0%low visibility |
| 128.0.172.113/32 | Valid | None | 3 0%low visibility |
| 185.38.209.68/32 | Valid | Nonecovered by 185.38.209.0/24 | 3 0%low visibility |
| 185.38.209.69/32 | Valid | Nonecovered by 185.38.209.0/24 | 3 0%low visibility |
| 185.38.209.71/32 | Valid | Nonecovered by 185.38.209.0/24 | 3 0%low visibility |
| 185.38.209.73/32 | Valid | Nonecovered by 185.38.209.0/24 | 3 0%low visibility |
| 185.38.209.74/32 | Valid | Nonecovered by 185.38.209.0/24 | 3 0%low visibility |
| 185.38.209.96/32 | Valid | Nonecovered by 185.38.209.0/24 | 3 0%low visibility |
| 185.38.209.97/32 | Valid | Nonecovered by 185.38.209.0/24 | 3 0%low visibility |
| 185.38.209.102/32 | Valid | Nonecovered by 185.38.209.0/24 | 3 0%low visibility |
| 185.39.196.43/32 | Valid | Nonecovered by 185.39.196.0/24 | 3 0%low visibility |
| 185.45.245.53/32 | Valid | Nonecovered by 185.45.245.0/24 | 3 0%low visibility |
| 212.110.134.51/32 | Valid | Nonecovered by 212.110.134.0/23 | 3 0%low visibility |
| 212.110.153.163/32 | Valid | Nonecovered by 212.110.152.0/23 | 3 0%low visibility |
| 31.172.136.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 31.172.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.172.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.172.140.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.172.141.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.117.229.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.90.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.202.108.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.226.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.60.178.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 92.60.178.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.60.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.38.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.39.196.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.45.245.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.45.246.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.170.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.111.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.111.48.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.246.121.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.110.134.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 80.92.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 128.0.170.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 128.0.174.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.110.152.0/23 | Valid | RIR databaseRIPE | 260 39% |
| 82.117.244.0/24 | Valid | RIR databaseRIPE | 259 38% |
| 85.90.211.0/24 | Valid | RIR databaseRIPE | 256 38% |
| 80.92.235.0/24 | Valid | RIR databaseRIPE | 108 16% |
AS-SET
AS24685 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 24 are in fix.csv.
- ROA: origin1
- Route object: none22
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 212.110.139.0/24 | ROAs covering it name AS1820, AS34136, not AS24685. If AS24685 should announce it, add a ROA for AS24685. |
| Route object: none | 212.110.139.0/24 | No route object for it. Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 80.92.233.0/24 | Route objects for it name AS21390, AS41540. Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 80.92.234.0/24 | Route objects for it name AS21390, AS41540. Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 128.0.172.0/24 | No route object for it. Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 194.28.198.0/24 | No route object for it. Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 85.90.211.48/32 | No route object for it. A route object for 85.90.211.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 85.90.211.217/32 | No route object for it. A route object for 85.90.211.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 85.90.211.221/32 | No route object for it. A route object for 85.90.211.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 92.60.179.130/32 | No route object for it. A route object for 92.60.179.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 128.0.172.113/32 | No route object for it. Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.38.209.68/32 | No route object for it. A route object for 185.38.209.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.38.209.69/32 | No route object for it. A route object for 185.38.209.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.38.209.71/32 | No route object for it. A route object for 185.38.209.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.38.209.73/32 | No route object for it. A route object for 185.38.209.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.38.209.74/32 | No route object for it. A route object for 185.38.209.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.38.209.96/32 | No route object for it. A route object for 185.38.209.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.38.209.97/32 | No route object for it. A route object for 185.38.209.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.38.209.102/32 | No route object for it. A route object for 185.38.209.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.39.196.43/32 | No route object for it. A route object for 185.39.196.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 185.45.245.53/32 | No route object for it. A route object for 185.45.245.0/24 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 212.110.134.51/32 | No route object for it. A route object for 212.110.134.0/23 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
| Route object: none | 212.110.153.163/32 | No route object for it. A route object for 212.110.152.0/23 with origin AS24685 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24685 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24685 whose prefix no peer sees AS24685 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a01:6b0:7::/48 | RIPE | Invalid: origin |
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.