Routing security
AS59616 BAIKAL-TELEPORT-AS Baikal Teleport CJSC
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS59616 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 91.246.0.0/22 | No ROA | IRR | 53 |
| 91.246.0.0/24 | No ROA | IRR | 53 |
| 91.246.1.0/24 | No ROA | IRR | 52 |
| 91.246.2.0/24 | No ROA | IRR | 53 |
| 91.246.3.0/24 | No ROA | IRR | 52 |
| 193.106.0.0/23 | No ROA | IRR | 52 |
| 193.106.0.0/24 | No ROA | IRR | 53 |
| 193.106.1.0/24 | No ROA | IRR | 53 |
| 193.106.2.0/24 | No ROA | IRR | 53 |
| 193.169.0.0/23 | No ROA | IRR | 53 |
| 193.169.0.0/24 | No ROA | IRR covering | 53 |
| 193.169.1.0/24 | No ROA | IRR covering | 52 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS59616 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 AS59616 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 |
|---|---|---|---|---|---|
| 2a05:a7c6::/32 | RIPE | — | MNT-BAIKAL-TELEPORT | 2023-11-15 | Not announced |
| 91.246.0.0/22 | RIPE | Baikal-Teleport CJSC | MNT-BAIKAL-TELEPORT | 2012-09-04 | Announced |
| 91.246.0.0/24 | RIPE | Baikal-Teleport CJSC | MNT-BAIKAL-TELEPORT | 2012-11-15 | Announced |
| 91.246.1.0/24 | RIPE | Baikal-Teleport CJSC | MNT-BAIKAL-TELEPORT | 2012-11-15 | Announced |
| 91.246.2.0/24 | RIPE | Baikal-Teleport CJSC | MNT-BAIKAL-TELEPORT | 2012-11-15 | Announced |
| 91.246.3.0/24 | RIPE | Baikal-Teleport CJSC | MNT-BAIKAL-TELEPORT | 2012-11-15 | Announced |
| 193.106.0.0/23 | RIPE | — | MNT-BAIKAL-TELEPORT | 2024-10-30 | Announced |
| 193.106.0.0/24 | RIPE | — | MNT-BAIKAL-TELEPORT | 2020-03-25 | Announced |
| 193.106.1.0/24 | RIPE | — | MNT-BAIKAL-TELEPORT | 2020-03-25 | Announced |
| 193.106.2.0/24 | RIPE | — | MNT-BAIKAL-TELEPORT | 2020-03-25 | Announced |
| 193.169.0.0/23 | RIPE | — | MNT-BAIKAL-TELEPORT | 2019-06-06 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS59616 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BTP | RIPE | Lists AS59616 as a direct member |
AS-DSIEAS | RIPE | Lists AS59616 as a direct member |
AS-HURRICANE | RADB | Lists AS59616 as a direct member |
AS-MEGATELECOM | RIPE | Lists AS59616 as a direct member |
AS-MTU | RIPE | Lists AS59616 as a direct member |
AS-MTU2 | RIPE | Lists AS59616 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS59616 as a direct member |
AS-SOVAM | RIPE | Lists AS59616 as a direct member |
AS-WEACOM | RIPE | Lists AS59616 as a direct member |
AS-WEACOMIX | RIPE | Lists AS59616 as a direct member |
AS209141:AS-RUCUST | RADB | Lists AS59616 as a direct member |
RPKI from rpki-client, validated 2026-11-07 13:08 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-07. Cross-check on bgp.he.net.