Skip to main content

AS28761

CrimeaCom-LLC

CrimeaCom South LTD. Autonomous system

Registry

Authoritative registration data

AS number
28761
Name
CrimeaCom-LLC
Organisation
CrimeaCom South LTD. Autonomous system
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

27

IPv6 prefixes

2

Total announced

29

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS28761
188.191.16.0/22 IPv4 /22 not checked
195.211.160.0/22 IPv4 /22 not checked
195.3.244.0/22 IPv4 /22 not checked
194.9.26.0/23 IPv4 /23 not checked
195.88.52.0/23 IPv4 /23 RPKI invalid
91.224.30.0/23 IPv4 /23 not checked
91.232.118.0/23 IPv4 /23 not checked
185.76.80.0/24 IPv4 /24 RPKI valid
188.191.16.0/24 IPv4 /24 not checked
188.191.17.0/24 IPv4 /24 not checked
188.191.18.0/24 IPv4 /24 not checked
188.191.19.0/24 IPv4 /24 not checked
188.191.24.0/24 IPv4 /24 RPKI valid
188.191.25.0/24 IPv4 /24 RPKI valid
188.191.26.0/24 IPv4 /24 RPKI valid
188.191.27.0/24 IPv4 /24 not checked
193.188.254.0/24 IPv4 /24 RPKI valid
193.238.109.0/24 IPv4 /24 RPKI not found
193.238.110.0/24 IPv4 /24 not checked
193.238.111.0/24 IPv4 /24 not checked
193.27.242.0/24 IPv4 /24 RPKI not found
193.27.243.0/24 IPv4 /24 RPKI not found
195.26.80.0/24 IPv4 /24 RPKI valid
195.26.81.0/24 IPv4 /24 not checked
91.194.163.0/24 IPv4 /24 not checked
91.232.116.0/24 IPv4 /24 not checked
91.232.119.0/24 IPv4 /24 not checked
2a05:5840::/32 IPv6 /32 RPKI valid
2a05:5841::/32 IPv6 /32 RPKI not found

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS28761
Address families
Crimea-IX 100,000 Mbps IPv4
GNM-IX 20,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS28761 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

27 networks seen before AS28761 in AS paths

No rows match “”.

Showing – of

Observed downstreams

53 networks seen after AS28761 in AS paths

Observed downstreams
Families
AS196705 Ardinvest 557 4,502
v4 v6
AS205515 Telesystems 536 3,719
v4
AS50949 agronet-ru-as 727 2,883
v4
AS47939 YALTANET 252 2,745
v4
AS57093 ASYALTA 284 2,512
v4
AS200420 RFMEGA-NET 306 1,804
v4
AS44341 SEVONLINE 549 1,798
v4
AS204144 COMFORT-AS 200 1,786
v4
AS43822 HOMEOPTIC 275 1,440
v4
AS208397 INFOSTROY-AS 261 1,189
v4
AS12507 SWIFT-TRACE-AS 319 1,081
v4
AS58000 MTN-NET-AS 280 1,080
v4
AS200922 YugTel-AS 277 1,080
v4
AS56587 ASCITADEL 285 728
v4
AS200441 CRIMEADC-NET 541 722
v4 v6
AS206448 SouthTransTelecom-AS 274 716
v4
AS59823 MTRIX-ALCHEVSK-AS 547 690
v4
AS204259 KAMETA-NET 285 690
v4
AS198669 KNET-AS 307 615
v4
AS197159 TriNet 83 527
v4
AS208456 AS-ITPARKRU 186 476
v4
AS50042 UBS 343 441
v4
AS200702 SPKVA-NET 125 413
v4
AS205236 GIPERCOM-NET 127 364
v4
AS34879 CCT-AS 276 360
v4
AS41308 TVOE-TV 275 360
v4
AS42253 TelSP 275 360
v4
AS44200 REVOLAN-AS 275 360
v4
AS49617 IZMV-AS 275 360
v4
AS207235 GURZUF-21-VEK-AS 275 360
v4
AS211382 Sevas 270 360
v4
AS204825 RESCOM-AS 288 355
v4
AS25203 SIMFINET-AS 289 352
v4
AS25118 POLUOSTROV-AS 288 352
v4
AS57899 MASANDRA-AS 288 352
v4
AS196716 CHNG-AS 288 352
v4
AS214767 yug-as 288 352
v4
AS197171 MEGATEL-AS 284 351
v4
AS204791 STARLINK-CRIMEA-AS 276 346
v4
AS35381 POLIGON-ISP 282 345
v4
AS48086 TRK555-AS 277 343
v4
AS50140 YALTA-AS 281 341
v4
AS12408 BIKENT-AS 261 332
v4
AS57629 IVI-RU 227 304
v6
AS51214 VIKS-NET 87 222
v4
AS198899 KSZ 163 207
v4
AS57679 TRK-TONUS-AS 80 206
v4
AS208701 Amos-as 157 199
v4
AS215705 MRIYA-LCC 144 182
v4
AS50654 LASPI-AS 142 177
v4
AS198293 GIGABYTE-AS 35 145
v4
AS44917 NN-KBKA-AS 86 107
v4
AS213258 CHYUS-NET-1 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.