Skip to main content

AS42514

SIGNAL-AS

--- Upstreams ---

Registry

Authoritative registration data

AS number
42514
Name
SIGNAL-AS
Organisation
--- Upstreams ---
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

1

Total announced

10

Announced prefixes

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

Prefixes announced by AS42514
128.204.160.0/19 IPv4 /19 RPKI valid
178.17.128.0/20 IPv4 /20 not checked
46.22.240.0/20 IPv4 /20 RPKI valid
94.102.16.0/20 IPv4 /20 not checked
95.141.176.0/20 IPv4 /20 RPKI valid
153.80.172.0/22 IPv4 /22 RPKI valid
185.12.84.0/22 IPv4 /22 not checked
213.166.76.0/22 IPv4 /22 RPKI valid
89.232.180.0/22 IPv4 /22 not checked
2a02:2648::/29 IPv6 /29 RPKI valid

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 AS42514
Address families
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4 · IPv6

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 AS42514 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS42514 in AS paths

Observed upstreams
Families
AS20485 TRANSTELECOM 143 800
v4 v6
AS12389 ROSTELECOM-AS 129 573
v4 v6
AS8359 MTS 69 354
v4 v6
AS31133 MF-MGSM-AS 90 287
v4 v6
AS25091 IP-Max 2 18
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS42514 in AS paths

Observed downstreams
Families
AS197717 MGOK-AS 146 170
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 18
v4
AS37721 ORG-VTS1-AFRINIC 1 9
v4
AS205112 PHILUNET 1 9
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.