Skip to main content

AS5523

CREDO-TELECOM

==================================================

Registry

Authoritative registration data

AS number
5523
Name
CREDO-TELECOM
Organisation
==================================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS5523
81.13.0.0/17 IPv4 /17 RPKI not found
194.67.128.0/18 IPv4 /18 RPKI not found
213.252.64.0/18 IPv4 /18 RPKI not found
194.67.224.0/19 IPv4 /19 not checked

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 AS5523
Address families
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4
PITER-IX Moscow: MSK_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 AS5523 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS5523 in AS paths

Observed upstreams
Families
AS35598 INETCOM 107 420
v4
AS3216 SOVAM-AS 96 276
v4
AS62255 BEMYLINK 83 208
v4
AS50509 TRANSROUTE 120 152
v4
AS25091 IP-Max 5 14
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS5523 in AS paths

Observed downstreams
Families
AS13161 TECHNOCOM 166 198
v4
AS203006 ITS-AS 89 107
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 10
v4
AS37721 ORG-VTS1-AFRINIC 3 6
v4
AS49673 TRUENETWORK 3 6
v4
AS49544 i3Dnet 2 5
v4

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.