Routing security
AS60330 BCTBY-AS Belarusian Cloud Technologies LLC
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS60330 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a0a:eac2::/48 | No ROA | IRR other origin | 34 |
| 217.21.36.251/32 | No ROA | No IRR | 1 |
| 2a00:c820::/32 | No ROA | IRR | 34 |
| 2a00:c827::/32 | No ROA | IRR | 34 |
| 93.125.20.0/24 | No ROA | IRR | 57 |
| 93.125.21.0/24 | No ROA | IRR | 57 |
| 93.125.22.0/24 | No ROA | IRR | 57 |
| 93.125.23.0/24 | No ROA | IRR | 57 |
| 93.125.24.0/23 | No ROA | IRR | 57 |
| 93.125.24.0/24 | No ROA | IRR | 57 |
| 93.125.25.0/24 | No ROA | IRR | 57 |
| 95.130.83.0/24 | No ROA | IRR | 57 |
| 95.130.85.0/24 | No ROA | IRR | 57 |
| 185.32.224.0/22 | No ROA | IRR | 57 |
| 195.50.4.0/22 | No ROA | IRR | 57 |
| 195.50.4.0/24 | No ROA | IRR | 57 |
| 195.50.5.0/24 | No ROA | IRR | 57 |
| 195.50.6.0/24 | No ROA | IRR | 57 |
| 195.50.7.0/24 | No ROA | IRR | 57 |
| 195.50.8.0/21 | No ROA | IRR | 57 |
| 195.50.8.0/24 | No ROA | IRR | 57 |
| 195.50.9.0/24 | No ROA | IRR | 57 |
| 195.50.11.0/24 | No ROA | IRR | 57 |
| 195.50.17.0/24 | No ROA | IRR | 57 |
| 195.50.18.0/24 | No ROA | IRR | 57 |
| 195.50.19.0/24 | No ROA | IRR | 57 |
| 195.50.20.0/24 | No ROA | IRR | 57 |
| 195.50.21.0/24 | No ROA | IRR | 57 |
| 195.50.22.0/24 | No ROA | IRR | 57 |
| 195.50.25.0/24 | No ROA | IRR | 57 |
| 195.50.26.0/24 | No ROA | IRR | 57 |
| 195.50.27.0/24 | No ROA | IRR | 57 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS60330 may originate these prefixes, up to the maximum length shown.
No ROA names this AS as an authorised origin.
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS60330 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 93.125.20.0/22 | RIPE | — | BCTBY-MNT | 2021-06-28 | Not announced |
| 185.32.224.0/24 | RIPE | BeCloud IPv4 route 1.1 | BCTBY-MNT | 2018-01-09 | Not announced |
| 185.32.225.0/24 | RIPE | BeCloud IPv4 route 1.2 | BCTBY-MNT | 2018-01-09 | Not announced |
| 185.32.226.0/24 | RIPE | BeCloud IPv4 route 1.3 | BCTBY-MNT | 2018-01-09 | Not announced |
| 185.32.227.0/24 | RIPE | BeCloud IPv4 route 1.4 | BCTBY-MNT | 2018-01-09 | Not announced |
| 195.50.16.0/22 | RIPE | BeCloud IPv4 route 195.50.16.0/22 | BCTBY-MNT | 2023-03-20 | Not announced |
| 195.50.16.0/24 | RIPE | BeCloud IPv4 route 195.50.16.0/24 | BCTBY-MNT | 2023-03-20 | Not announced |
| 195.50.28.0/24 | RIPE | BeCloud IPv4 AC1 | BCTBY-MNT | 2026-02-12 | Not announced |
| 195.50.29.0/24 | RIPE | BeCloud IPv4 AC2 | BCTBY-MNT | 2026-02-12 | Not announced |
| 2001:7f9:10::/48 | RIPE | beCloud IPv6 AC | BCTBY-MNT | 2026-02-20 | Not announced |
| 2a00:c820::/29 | RIPE | beCloud IPv6 block # 2 | BCTBY-MNT | 2019-03-25 | Not announced |
| 2a00:c821::/32 | RIPE | beCloud IPv6 block # 2.2 | BCTBY-MNT | 2019-03-25 | Not announced |
| 2a00:c822::/32 | RIPE | beCloud IPv6 block # 2.3 | BCTBY-MNT | 2019-03-25 | Not announced |
| 2a00:c823::/32 | RIPE | beCloud IPv6 block # 2.4 | BCTBY-MNT | 2019-03-25 | Not announced |
| 2a00:c824::/32 | RIPE | beCloud IPv6 block # 2.5 | BCTBY-MNT | 2019-03-25 | Not announced |
| 2a00:c825::/32 | RIPE | beCloud IPv6 block # 2.6 | BCTBY-MNT | 2019-03-25 | Not announced |
| 2a00:c826::/32 | RIPE | beCloud IPv6 block # 2.7 | BCTBY-MNT | 2019-03-25 | Not announced |
| 93.125.20.0/24 | RIPE | BeCloud IPv4 route 4.1 | BCTBY-MNT | 2019-03-25 | Announced |
| 93.125.21.0/24 | RIPE | BeCloud IPv4 route 4.2 | BCTBY-MNT | 2019-03-25 | Announced |
| 93.125.22.0/24 | RIPE | BeCloud IPv4 route 4.3 | BCTBY-MNT | 2019-03-25 | Announced |
| 93.125.23.0/24 | RIPE | BeCloud IPv4 route 4.4 | BCTBY-MNT | 2019-03-25 | Announced |
| 93.125.24.0/23 | RIPE | — | BCTBY-MNT | 2021-06-28 | Announced |
| 93.125.24.0/24 | RIPE | BeCloud IPv4 route 4.5 | BCTBY-MNT | 2019-03-25 | Announced |
| 93.125.25.0/24 | RIPE | BeCloud IPv4 route 4.6 | BCTBY-MNT | 2019-03-25 | Announced |
| 95.130.83.0/24 | RIPE | LLC Raccoon technology | BCTBY-MNT | 2025-03-11 | Announced |
| 95.130.85.0/24 | RIPE | LLC Raccoon technology | BCTBY-MNT | 2022-01-13 | Announced |
| 185.32.224.0/22 | RIPE | BeCloud IPv4 route 1 | BCTBY-MNT | 2016-07-01 | Announced |
| 195.50.4.0/22 | RIPE | BeCloud IPv4 route 2 | BCTBY-MNT | 2016-07-01 | Announced |
| 195.50.4.0/24 | RIPE | BeCloud | BCTBY-MNT | 2025-01-13 | Announced |
| 195.50.5.0/24 | RIPE | BeCloud | BCTBY-MNT | 2025-01-13 | Announced |
| 195.50.6.0/24 | RIPE | — | BCTBY-MNT | 2023-03-20 | Announced |
| 195.50.7.0/24 | RIPE | BeCloud | BCTBY-MNT | 2025-01-13 | Announced |
| 195.50.8.0/21 | RIPE | BeCloud IPv4 route 3 | BCTBY-MNT | 2016-09-01 | Announced |
| 195.50.8.0/24 | RIPE | BeCloud IPv4 route 3.1 | BCTBY-MNT | 2017-10-07 | Announced |
| 195.50.9.0/24 | RIPE | BeCloud | BCTBY-MNT | 2025-01-13 | Announced |
| 195.50.11.0/24 | RIPE | BeCloud IPv4 route tst | BCTBY-MNT | 2017-04-06 | Announced |
| 195.50.17.0/24 | RIPE | BeCloud IPv4 route 195.50.17.0/24 | BCTBY-MNT | 2023-03-20 | Announced |
| 195.50.18.0/24 | RIPE | BeCloud IPv4 route 195.50.18.0/24 | BCTBY-MNT | 2023-03-20 | Announced |
| 195.50.19.0/24 | RIPE | BeCloud IPv4 route 195.50.19.0/24 | BCTBY-MNT | 2023-03-20 | Announced |
| 195.50.20.0/24 | RIPE | BeCloud IPv4 route 195.50.20.0/24 | BCTBY-MNT | 2024-02-15 | Announced |
| 195.50.21.0/24 | RIPE | BeCloud IPv4 route 195.50.21.0/24 | BCTBY-MNT | 2024-02-15 | Announced |
| 195.50.22.0/24 | RIPE | BeCloud IPv4 route 195.50.22.0/24 | BCTBY-MNT | 2024-02-15 | Announced |
| 195.50.25.0/24 | RIPE | BeCloud IPv4 route 195.50.25.0/24 | BCTBY-MNT | 2025-03-10 | Announced |
| 195.50.26.0/24 | RIPE | BeCloud IPv4 route 195.50.26.0/24 | BCTBY-MNT | 2025-03-10 | Announced |
| 195.50.27.0/24 | RIPE | BeCloud IPv4 route 195.50.27.0/24 | BCTBY-MNT | 2025-03-10 | Announced |
| 2a00:c820::/32 | RIPE | beCloud IPv6 block # 2.1 | BCTBY-MNT | 2019-03-25 | Announced |
| 2a00:c827::/32 | RIPE | beCloud IPv6 block # 2.8 | BCTBY-MNT | 2019-03-25 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS60330 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BECLOUD | RIPE | Lists AS60330 as a direct member |
AS-BECLOUD-BYIX | RIPE | Lists AS60330 as a direct member |
AS-HURRICANE | RADB | Lists AS60330 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS60330 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS60330 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS60330 as a direct member |
RPKI from rpki-client, validated 2026-11-05 13:06 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-05. Cross-check on bgp.he.net.