Skip to main content

AS44123

TELAVOX

+----------------------------------------------------+

Registry

Authoritative registration data

AS number
44123
Name
TELAVOX
Organisation
+----------------------------------------------------+
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

1

Total announced

13

Announced prefixes

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

Prefixes announced by AS44123
80.83.208.0/20 IPv4 /20 not checked
130.117.196.0/22 IPv4 /22 not checked
130.117.200.0/22 IPv4 /22 not checked
130.117.193.0/24 IPv4 /24 not checked
130.117.194.0/24 IPv4 /24 not checked
130.117.204.0/24 IPv4 /24 not checked
193.32.132.0/24 IPv4 /24 not checked
80.83.212.0/24 IPv4 /24 not checked
80.83.213.0/24 IPv4 /24 not checked
80.83.214.0/24 IPv4 /24 not checked
80.83.215.0/24 IPv4 /24 not checked
80.83.220.0/24 IPv4 /24 not checked
2a00:1690::/32 IPv6 /32 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 AS44123
Address families
Netnod Copenhagen BLUE -- MTU9K: 9K-BLUE 1,000 Mbps IPv4 · IPv6
Netnod Copenhagen GREEN -- MTU9K: 9K-GREEN 1,000 Mbps IPv4 · IPv6
Netnod Stockholm BLUE -- MTU1500: STH-B -- MTU1500 100 Mbps IPv4 · IPv6
Netnod Stockholm GREEN -- MTU1500: STH-A -- MTU1500 100 Mbps IPv4 · IPv6
STHIX - Stockholm: STH Peering 1,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 AS44123 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

40 networks seen before AS44123 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS44123 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

33 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.