Prefix | IP Count | Visibility | IRR | RPKI | Domain | Organization |
---|---|---|---|---|---|---|
95.161.64.0/20 | 4,094 | High:95% | RIPE | Valid | telegram.org |
MNT-GLOBAL-NET
|
91.108.4.0/22 | 1,022 | High:95% | RIPE | Valid | telegram.org |
MNT-TELEGRAM
|
91.108.8.0/22 | 1,022 | High:95% | RIPE | Valid | telegram.org |
MNT-TELEGRAM
|
149.154.164.0/22 | 1,022 | High:95% | RIPE | Valid | telegram.org |
Telegram_Messenger_Network
|
149.154.160.0/22 | 1,022 | High:95% | RIPE | Valid | telegram.org |
MNT-TELEGRAM
|
149.154.160.0/23 | 510 | High:95% | RIPE | Valid | telegram.org |
Telegram_Messenger_Network
|
149.154.162.0/23 | 510 | High:95% | RIPE | Valid | telegram.org |
Telegram_Messenger_Network
|
149.154.164.0/23 | 510 | High:95% | RIPE | Valid | telegram.org |
Telegram_Messenger_Network
|
149.154.166.0/23 | 510 | High:95% | RIPE | Valid | telegram.org |
Telegram_Messenger_Network
|
91.108.56.0/22 | 1,022 | High:90% | RIPE | Valid | telegram.org |
MNT-TELEGRAM
|
2001:67c:4e8::/48 | - | High:88% | RIPE | Valid | telegram.org |
MNT-TELEGRAM
|
AS62041
RIPE-NCC-END-MNT
Name | Telegram |
---|---|
Status | Active |
Country | - |
Website |
Type | Hosting |
---|---|
Total Prefixes | 11 |
Valid RPKI | 100% |
Est. Population | - |
Registry | RIPE |
---|---|
Age | |
Allocated | |
Last Updated |
IPv4
Prefix | Distribution. | Valid | Unknown | Invalid | Total | Perc. |
---|---|---|---|---|---|---|
/20 | 1 | 0 | 0 | 1 | 10% | |
/22 | 5 | 0 | 0 | 5 | 50% | |
/23 | 4 | 0 | 0 | 4 | 40% | |
Total | 10 | 0 | 0 | 10 | 100% |
IPv6
Prefix | Distribution. | Valid | Unknown | Invalid | Total | Perc. |
---|---|---|---|---|---|---|
/48 | 1 | 0 | 0 | 1 | 100% | |
Total | 1 | 0 | 0 | 1 | 100% |
ABOUTResource Public Key Infrastructure is a specialized public key infrastructure framework to improve security for the Internet's BGP routing infrastructure. RPKI provides a way to connect Internet number resource information (such as ASN and IP addresses) to a trust anchor. Wikipedia ↗︎
Upstreams — Any direct adjacent ASN in an AS path sequence that leads to a tier 1 ASN.
ASN | Organization |
---|---|
AS174 | Cogent Communications |
AS1273 | CW-EUROPE-GSOC |
AS3356 | Level 3 Parent, LLC |
AS5511 | RIPE-NCC-END-MNT |
AS6762 | RIPE-NCC-END-MNT |
AS6939 | Hurricane Electric LLC |
AS9002 | RETN Limited |
AS12956 |
|
Downstreams — Any direct adjacent ASN in an AS path sequence that adds one-hop away from a tier 1 ASN.
No downstream connectivity detected for AS62041 at this time. Next update in ~3 hours.
Peers — Any direct adjacent ASN, can include upstreams, downstreams or tier 1 ASN.
ASN | Organization |
---|---|
AS174 | Cogent Communications |
AS1031 | Peer 1 Internet Service LLC |
AS1103 |
|
AS1140 |
|
AS1273 | CW-EUROPE-GSOC |
AS3214 | xtom |
AS3216 |
|
AS3356 | Level 3 Parent, LLC |
AS3399 | RIPE-NCC-END-MNT |
AS5511 | RIPE-NCC-END-MNT |
AS6762 | RIPE-NCC-END-MNT |
AS6939 | Hurricane Electric LLC |
AS8220 |
|
AS8529 | RIPE-NCC-END-MNT |
AS8888 | xtom |
AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC |
AS9002 | RETN Limited |
AS9902 | NeocomISP Limited |
AS12779 |
|
AS12859 | BIT BV |
AS12956 |
|
AS13237 | RIPE-NCC-END-MNT |
AS14537 | Continent 8 LLC |
AS16552 | Tiggee LLC |
AS18106 | Viewqwest Pte Ltd |
AS34288 | RIPE-NCC-END-MNT |
AS34549 | RIPE-NCC-END-MNT |
AS34927 | RIPE-NCC-END-MNT |
AS38880 | Micron21 Datacentre Pty Ltd |
AS39120 | RIPE-NCC-END-MNT |
AS39122 | RIPE-NCC-END-MNT |
AS39591 |
|
AS41805 | SAWAD LAND for Information Technology Ltd |
AS42541 | RIPE-NCC-END-MNT |
AS45352 | IP ServerOne Solutions Sdn Bhd |
AS47787 | RIPE-NCC-END-MNT |
AS49544 | RIPE-NCC-END-MNT |
AS50304 | RIPE-NCC-END-MNT |
AS50763 | RIPE-NCC-END-MNT |
AS51088 | A2B IP B.V. |
AS56662 | RIPE-NCC-END-MNT |
AS59605 | Zain Omantel International FZ-LLC |
AS61568 | ALOO TELECOM - FSF TECNOLOGIA SA |
AS63927 | RISE ASIA TECHNOLOGY LIMITED |
AS137409 | GSL Networks Pty LTD |
AS199524 | G-Core Labs S.A. |
AS213151 | RIPE-NCC-END-MNT |
AS328832 | Network Platforms (PTY) LTD |
Name | Location | Addresses | Link | RS Peer |
---|---|---|---|---|
AMS-IX
Amsterdam Internet Exchange
|
Amsterdam
|
80.249.209.69
2001:7f8:1::a506:2041:1 |
400 Gbps
Ethernet |
YES |
AMS-IX
Amsterdam Internet Exchange
|
Amsterdam
|
80.249.214.239
2001:7f8:1::a506:2041:4 |
400 Gbps
Ethernet |
YES |
AMS-IX
Amsterdam Internet Exchange
|
Amsterdam
|
80.249.214.57
2001:7f8:1::a506:2041:3 |
400 Gbps
Ethernet |
YES |
AMS-IX
Amsterdam Internet Exchange
|
Amsterdam
|
80.249.214.80
2001:7f8:1::a506:2041:2 |
400 Gbps
Ethernet |
YES |
DATAIX
GlobalNet
|
Frankfurt, Stockholm, Helsinki, Amsterdam, Sofia, St.Petersburg, Moscow, Ekaterinburg, Ufa, Novosibirsk, Kiev, Kharkov, Odessa, Samara, Chelyabinsk
|
178.18.225.141
2a03:5f80:4::225:141 |
600 Gbps
Multiple |
YES |
DATAIX
GlobalNet
|
Frankfurt, Stockholm, Helsinki, Amsterdam, Sofia, St.Petersburg, Moscow, Ekaterinburg, Ufa, Novosibirsk, Kiev, Kharkov, Odessa, Samara, Chelyabinsk
|
178.18.226.168
2a03:5f80:4::226:168 |
600 Gbps
Multiple |
YES |
DATAIX
GlobalNet
|
Frankfurt, Stockholm, Helsinki, Amsterdam, Sofia, St.Petersburg, Moscow, Ekaterinburg, Ufa, Novosibirsk, Kiev, Kharkov, Odessa, Samara, Chelyabinsk
|
178.18.227.113
2a03:5f80:4::227:113 |
600 Gbps
Multiple |
YES |
DATAIX
GlobalNet
|
Frankfurt, Stockholm, Helsinki, Amsterdam, Sofia, St.Petersburg, Moscow, Ekaterinburg, Ufa, Novosibirsk, Kiev, Kharkov, Odessa, Samara, Chelyabinsk
|
178.18.227.6
2a03:5f80:4::227:6 |
600 Gbps
Multiple |
YES |
DE-CIX Frankfurt
-
|
Frankfurt
|
80.81.193.148
2001:7f8::f259:0:1 |
400 Gbps
Ethernet |
YES |
DE-CIX Frankfurt
-
|
Frankfurt
|
80.81.196.155
2001:7f8::f259:0:2 |
400 Gbps
Ethernet |
YES |
DE-CIX Frankfurt
-
|
Frankfurt
|
80.81.196.179
2001:7f8::f259:0:3 |
400 Gbps
Ethernet |
YES |
DE-CIX Frankfurt
-
|
Frankfurt
|
80.81.196.184
2001:7f8::f259:0:4 |
400 Gbps
Ethernet |
YES |
Global-IX
GlobalNet
|
Amsterdam
|
109.239.136.22
2001:b28:3ff::f259:2 |
600 Gbps
Ethernet |
YES |
Global-IX
GlobalNet
|
Amsterdam
|
109.239.136.225
2001:b28:3ff::f259:1 |
600 Gbps
Ethernet |
YES |
ABOUTInternet Exchange Points (IXes or IXPs) are physical places where infrastructure companies interconnect with each other to exchange data destined for their respective networks. These locations are critical for companies to shorten their connection paths to other network participant, this allows for reduced round-trip time and low latency. Wikipedia ↗︎
Registrant
Handle | RIPE-NCC-END-MNT ↗︎ |
---|---|
Type | Individual |
Country | - |
Name | RIPE-NCC-END-MNT |
- | |
Phone | - |
Address | - |
Under the same Registrant
No other ASN registered under the same Registrant handle (RIPE-NCC-END-MNT).
Administrator
Handle | ND2624-RIPE ↗︎ |
---|---|
Type | Individual |
Country | - |
Name | Nikolai Durov |
- | |
Phone | +357 96 287319 |
Address | P.O. Box 146, Road Town, Tortola, British Virgin Islands MAP ↗︎ |
Abuse
Handle | TMI12-RIPE ↗︎ |
---|---|
Type | Group |
Country | - |
Name | Telegram Messenger Inc |
[email protected] | |
Phone | - |
Address | Telegram Messenger Inc, Trident House, Road Town, Tortola, BVI MAP ↗︎ |
Technical
Handle | ND2624-RIPE ↗︎ |
---|---|
Type | Individual |
Country | - |
Name | Nikolai Durov |
- | |
Phone | +357 96 287319 |
Address | P.O. Box 146, Road Town, Tortola, British Virgin Islands MAP ↗︎ |