Network · data from 2026-11-12
AS212046 MEZON-LT UAB "Bite Lietuva"
Registry name: MEZON-LT UAB "Bite Lietuva", LT · not in PeeringDB
47IPv4 routes
100.0% RPKI valid · 51.1% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
23 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS212046, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS212046, 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.
| 84.46.136.0/24 | Valid | None | 671 100% |
| 84.46.146.0/24 | Valid | None | 671 100% |
| 84.46.147.0/24 | Valid | None | 671 100% |
| 84.46.148.0/24 | Valid | None | 671 100% |
| 84.46.149.0/24 | Valid | None | 671 100% |
| 84.46.168.0/24 | Valid | None | 671 100% |
| 84.46.169.0/24 | Valid | None | 671 100% |
| 86.38.18.0/24 | Valid | None | 671 100% |
| 86.38.28.0/24 | Valid | None | 671 100% |
| 86.38.29.0/24 | Valid | None | 671 100% |
| 86.38.30.0/24 | Valid | None | 671 100% |
| 86.38.31.0/24 | Valid | None | 671 100% |
| 86.38.38.0/24 | Valid | None | 671 100% |
| 86.38.39.0/24 | Valid | None | 671 100% |
| 86.38.161.0/24 | Valid | None | 671 100% |
| 86.38.165.0/24 | Valid | None | 671 100% |
| 86.38.166.0/24 | Valid | None | 671 100% |
| 86.38.167.0/24 | Valid | None | 671 100% |
| 86.38.168.0/24 | Valid | None | 671 100% |
| 86.38.169.0/24 | Valid | None | 671 100% |
| 86.38.171.0/24 | Valid | None | 671 100% |
| 86.38.173.0/24 | Valid | None | 671 100% |
| 89.117.140.0/24 | Valid | None | 671 100% |
| 82.140.133.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.140.152.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.140.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.140.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.140.184.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.140.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 84.46.160.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 84.46.161.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 84.46.162.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 84.46.163.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 84.46.205.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.38.6.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.38.33.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.38.174.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.38.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.38.188.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 86.38.201.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.116.238.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.116.240.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.116.245.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.116.249.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.117.128.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.9.240.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.9.243.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS212046 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 25 are in fix.csv.
- Route object: none23
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 84.46.136.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 84.46.146.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 84.46.147.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 84.46.148.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 84.46.149.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 84.46.168.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 84.46.169.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.18.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.28.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.29.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.30.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.31.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.38.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.39.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.161.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.165.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.166.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.167.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.168.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.169.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.171.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 86.38.173.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
| Route object: none | 89.117.140.0/24 | No route object for it. Add a route object with origin AS212046 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS212046 whose prefix no peer sees AS212046 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.116.143.0/24 | RIPE | Valid |
| 89.116.151.0/24 | 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.