Routing security
AS20632 PETERSTAR-AS Saint-Petersburg
Unclassified RIPE
RPKI valid
100%
66 of 66 announcements
RPKI invalid
0
none
No ROA
0
not covered by any ROA
IRR registered
98%
0 missing · 1 other origin
ROAs
68
authorising this AS
Announcements
What this network originates
Every prefix observed with AS20632 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 94.25.248.0/21 | RPKI valid | IRR other origin | 53 |
| 2a03:d000:9008::/46 | RPKI valid | IRR | 34 |
| 2a03:d000:9008::/48 | RPKI valid | IRR | 34 |
| 2a03:d000:9009::/48 | RPKI valid | IRR | 34 |
| 46.47.192.0/18 | RPKI valid | IRR | 52 |
| 46.47.202.0/24 | RPKI valid | IRR | 52 |
| 62.16.99.0/24 | RPKI valid | IRR | 52 |
| 62.16.101.0/24 | RPKI valid | IRR | 52 |
| 62.16.102.0/24 | RPKI valid | IRR | 52 |
| 62.16.103.0/24 | RPKI valid | IRR | 52 |
| 62.16.104.0/24 | RPKI valid | IRR | 52 |
| 62.16.105.0/24 | RPKI valid | IRR | 52 |
| 62.16.106.0/24 | RPKI valid | IRR | 52 |
| 62.16.107.0/24 | RPKI valid | IRR | 52 |
| 62.16.108.0/24 | RPKI valid | IRR | 52 |
| 62.16.109.0/24 | RPKI valid | IRR | 52 |
| 62.16.112.0/24 | RPKI valid | IRR | 52 |
| 62.16.117.0/24 | RPKI valid | IRR | 52 |
| 62.16.119.0/24 | RPKI valid | IRR | 52 |
| 62.182.128.0/21 | RPKI valid | IRR | 52 |
| 79.171.8.0/21 | RPKI valid | IRR | 52 |
| 80.247.176.0/20 | RPKI valid | IRR | 52 |
| 81.3.128.0/18 | RPKI valid | IRR | 52 |
| 81.24.128.0/20 | RPKI valid | IRR | 52 |
| 82.140.64.0/18 | RPKI valid | IRR | 52 |
| 82.140.93.0/24 | RPKI valid | IRR | 52 |
| 82.196.64.0/19 | RPKI valid | IRR | 52 |
| 84.204.0.0/17 | RPKI valid | IRR | 53 |
| 84.204.132.0/22 | RPKI valid | IRR | 53 |
| 84.204.136.0/24 | RPKI valid | IRR | 53 |
| 84.204.138.0/24 | RPKI valid | IRR | 53 |
| 84.204.139.0/24 | RPKI valid | IRR | 53 |
| 84.204.140.0/22 | RPKI valid | IRR | 53 |
| 84.204.144.0/20 | RPKI valid | IRR | 53 |
| 84.204.160.0/20 | RPKI valid | IRR | 53 |
| 84.204.176.0/21 | RPKI valid | IRR | 53 |
| 84.204.188.0/22 | RPKI valid | IRR | 53 |
| 84.204.192.0/18 | RPKI valid | IRR | 53 |
| 84.204.230.0/24 | RPKI valid | IRR | 53 |
| 91.193.212.0/22 | RPKI valid | IRR | 52 |
| 93.153.128.0/17 | RPKI valid | IRR | 52 |
| 93.153.144.0/21 | RPKI valid | IRR | 52 |
| 93.153.161.0/24 | RPKI valid | IRR | 52 |
| 93.153.162.0/24 | RPKI valid | IRR | 52 |
| 95.137.0.0/17 | RPKI valid | IRR | 52 |
| 109.74.112.0/20 | RPKI valid | IRR | 52 |
| 109.124.64.0/18 | RPKI valid | IRR | 52 |
| 109.124.108.0/22 | RPKI valid | IRR | 52 |
| 176.192.126.0/24 | RPKI valid | IRR | 52 |
| 176.192.127.0/24 | RPKI valid | IRR | 52 |
| 195.5.128.0/19 | RPKI valid | IRR | 52 |
| 195.131.14.0/24 | RPKI valid | IRR | 52 |
| 195.131.38.0/24 | RPKI valid | IRR | 52 |
| 195.144.224.0/19 | RPKI valid | IRR | 52 |
| 212.14.160.0/19 | RPKI valid | IRR | 52 |
| 212.44.64.0/19 | RPKI valid | IRR | 52 |
| 212.48.155.0/24 | RPKI valid | IRR | 53 |
| 212.119.160.0/19 | RPKI valid | IRR | 52 |
| 213.154.160.0/21 | RPKI valid | IRR | 53 |
| 213.154.168.0/21 | RPKI valid | IRR | 53 |
| 213.154.176.0/21 | RPKI valid | IRR | 53 |
| 213.154.184.0/21 | RPKI valid | IRR | 53 |
| 213.168.32.0/19 | RPKI valid | IRR | 52 |
| 213.172.0.0/19 | RPKI valid | IRR | 52 |
| 213.182.160.0/19 | RPKI valid | IRR | 52 |
| 217.195.64.0/19 | RPKI valid | IRR | 52 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS20632 may originate these prefixes, up to the maximum length shown.
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 AS20632 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 |
|---|---|---|---|---|---|
| 46.151.172.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Not announced |
| 62.89.224.0/19 | RIPE | RU-INAR Yaroslavl Block | INAR-RIPE-MNT | 2019-06-04 | Not announced |
| 82.140.96.0/22 | RIPE | ZAO PeterStar | PSTAR-MNT | 2008-08-11 | Not announced |
| 82.196.95.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.1.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.64.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.106.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.107.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.109.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.110.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.111.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.112.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.113.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.121.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.122.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.156.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.184.0/22 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 84.204.252.0/22 | RIPE | ZAO PeterStar | PSTAR-MNT | 2006-12-25 | Not announced |
| 84.204.255.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 93.153.128.0/18 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 93.153.158.0/24 | RIPE | ZAO PeterStar | PSTAR-MNT | 2008-08-11 | Not announced |
| 93.153.216.0/22 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Not announced |
| 109.124.113.0/24 | RIPE | JSC Peterstar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 109.124.114.0/24 | RIPE | JSC Peterstar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 213.172.0.0/20 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 213.172.10.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 213.172.11.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 213.172.16.0/21 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 213.172.23.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 213.172.24.0/22 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 217.195.77.0/24 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-24 | Not announced |
| 2a03:d003::/36 | RIPE | — | MEGAFON-RIPE-MNT | 2024-12-19 | Not announced |
| 46.47.192.0/18 | RIPE | PJSC Megafon SZF | MEGAFON-RIPE-MNT | 2020-02-25 | Announced |
| 46.47.202.0/24 | RIPE | OJSC Megafon, NW Branch | MNT-MF-NWGSM | 2026-04-24 | Announced |
| 62.16.99.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-06-10 | Announced |
| 62.16.101.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.102.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.103.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.104.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.105.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.106.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.107.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.108.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.109.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.112.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.117.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.16.119.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 62.182.128.0/21 | RIPE | — | MNT-MF-NWGSM | 2022-05-30 | Announced |
| 79.171.8.0/21 | RIPE | North-West Branch of PJSC MegaFon | MEGAFON-RIPE-MNT | 2020-02-25 | Announced |
| 80.247.176.0/20 | RIPE | North-West Branch of PJSC MegaFon | MEGAFON-RIPE-MNT | 2020-05-14 | Announced |
| 81.3.128.0/18 | RIPE | North-West Branch of PJSC MegaFon | MEGAFON-RIPE-MNT | 2020-02-25 | Announced |
| 81.24.128.0/20 | RIPE | — | MNT-MF-NWGSM | 2022-05-30 | Announced |
| 82.140.64.0/18 | RIPE | North-West Branch of PJSC MegaFon | MEGAFON-RIPE-MNT | 2020-02-25 | Announced |
| 82.140.93.0/24 | RIPE | — | MNT-MF-NWGSM | 2023-09-12 | Announced |
| 82.196.64.0/19 | RIPE | North-West Branch of PJSC MegaFon | MEGAFON-RIPE-MNT | 2020-02-25 | Announced |
| 84.204.0.0/17 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Announced |
| 84.204.132.0/22 | RIPE | Peterstar at Kaliningrad | PSTAR-MNT | 2010-07-14 | Announced |
| 84.204.136.0/24 | RIPE | JSC PeterStar | PSTAR-MNT | 2009-12-01 | Announced |
| 84.204.138.0/24 | RIPE | ZAO PeterStar | PSTAR-MNT | 2008-05-29 | Announced |
| 84.204.139.0/24 | RIPE | JSC PeterStar | PSTAR-MNT | 2009-12-01 | Announced |
| 84.204.140.0/22 | RIPE | Peterstar at Kaliningrad | MNT-MF-NWGSM | 2022-11-29 | Announced |
| 84.204.144.0/20 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Announced |
| 84.204.160.0/20 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Announced |
| 84.204.176.0/21 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Announced |
| 84.204.188.0/22 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Announced |
| 84.204.192.0/18 | RIPE | ZAO PeterStar | MNT-MF-NWGSM | 2022-11-29 | Announced |
| 84.204.230.0/24 | RIPE | — | MNT-MF-NWGSM | 2023-08-24 | Announced |
| 91.193.212.0/22 | RIPE | — | MNT-MF-NWGSM | 2022-05-30 | Announced |
| 93.153.128.0/17 | RIPE | North-West Branch of PJSC MegaFon | MEGAFON-RIPE-MNT | 2020-02-25 | Announced |
| 93.153.144.0/21 | RIPE | PeterStar at Kaliningrad | PSTAR-MNT | 2010-07-27 | Announced |
| 93.153.161.0/24 | RIPE | — | MNT-MF-NWGSM | 2021-11-23 | Announced |
| 93.153.162.0/24 | RIPE | — | MNT-MF-NWGSM | 2021-11-23 | Announced |
| 95.137.0.0/17 | RIPE | North-West Branch of PJSC MegaFon | MEGAFON-RIPE-MNT | 2020-05-14 | Announced |
| 109.74.112.0/20 | RIPE | PJSC MegaFon - exSZKTI (AS41976) | MNT-MF-NWGSM | 2023-08-07 | Announced |
| 109.124.64.0/18 | RIPE | North-West Branch of PJSC MegaFon | MEGAFON-RIPE-MNT | 2020-02-25 | Announced |
| 109.124.108.0/22 | RIPE | PeterStar at Kaliningrad | MNT-MF-NWGSM | 2022-11-24 | Announced |
| 176.192.126.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 176.192.127.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 195.5.128.0/19 | RIPE | PJSC "Megafon" | MEGAFON-RIPE-MNT | 2020-03-04 | Announced |
| 195.131.14.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 195.131.38.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-04-15 | Announced |
| 195.144.224.0/19 | RIPE | PJSC "Megafon" | MEGAFON-RIPE-MNT | 2020-03-04 | Announced |
| 212.14.160.0/19 | RIPE | Fixed - Arkhangelsk Megafon (ex-RU-INAR Block) | MEGAFON-RIPE-MNT | 2020-03-04 | Announced |
| 212.44.64.0/19 | RIPE | PJSC "Megafon" | MEGAFON-RIPE-MNT | 2020-03-04 | Announced |
| 212.48.155.0/24 | RIPE | PJSC MegaFon SZF prefix | TI-MNT | 2026-08-07 | Announced |
| 212.119.160.0/19 | RIPE | PJSC "Megafon" | MEGAFON-RIPE-MNT | 2020-03-04 | Announced |
| 213.154.160.0/21 | RIPE | Vologda | MNT-MF-NWGSM | 2023-11-07 | Announced |
| 213.154.168.0/21 | RIPE | — | MNT-MF-NWGSM | 2023-11-09 | Announced |
| 213.154.176.0/21 | RIPE | — | MNT-MF-NWGSM | 2023-11-09 | Announced |
| 213.154.184.0/21 | RIPE | — | MNT-MF-NWGSM | 2023-11-09 | Announced |
| 213.168.32.0/19 | RIPE | PJSC "Megafon" ex.AS41976 | MNT-MF-NWGSM | 2023-08-10 | Announced |
| 213.172.0.0/19 | RIPE | PJSC "Megafon" | MEGAFON-RIPE-MNT | 2020-03-06 | Announced |
| 213.182.160.0/19 | RIPE | PJSC "Megafon" | MEGAFON-RIPE-MNT | 2020-05-14 | Announced |
| 217.195.64.0/19 | RIPE | PJSC "Megafon" | MEGAFON-RIPE-MNT | 2020-03-06 | Announced |
| 2a03:d000:9008::/46 | RIPE | — | MNT-MF-NWGSM | 2023-08-23 | Announced |
| 2a03:d000:9008::/48 | RIPE | — | MNT-MF-NWGSM | 2020-06-25 | Announced |
| 2a03:d000:9009::/48 | RIPE | — | MNT-MF-NWGSM | 2023-08-23 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS20632 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BLOCK-SET | RIPE | Lists AS20632 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS20632 as a direct member |
AS-BTN-CUSTOMERS | RADB | Lists AS20632 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS20632 as a direct member |
AS-METROCOM | RIPE | Lists AS20632 as a direct member |
AS-MF-MGSM | RIPE | Lists AS20632 as a direct member |
AS-PETERSTAR-C | RIPE | Lists AS20632 as a direct member |
AS-PETERSTAR-KNG | RIPE | Lists AS20632 as a direct member |
AS-PETERSTAR-M9 | RIPE | Lists AS20632 as a direct member |
AS-PETERSTAR-NW | RIPE | Lists AS20632 as a direct member |
AS-PETERSTAR-PSKOV | RIPE | Lists AS20632 as a direct member |
AS-PETERSTAR-PTZ | RIPE | Lists AS20632 as a direct member |
AS-PETERSTAR-VOLOGDA | RIPE | Lists AS20632 as a direct member |
AS-RELSPEER | RIPE | Lists AS20632 as a direct member |
AS-SYNTERRA | RIPE | Lists AS20632 as a direct member |
AS-SZKTI | RIPE | Lists AS20632 as a direct member |
RPKI from rpki-client, validated 2026-10-13 12:16 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-13. Cross-check on bgp.he.net.