Skip to main content

AS49769

Teracom-AB

Teracom AB

Registry

Authoritative registration data

AS number
49769
Name
Teracom-AB
Organisation
Teracom AB
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS49769
185.153.156.0/23 IPv4 /23 not checked
185.153.158.0/24 IPv4 /24 not checked
193.235.2.0/24 IPv4 /24 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 AS49769
Address families
Netnod Stockholm BLUE -- MTU1500: STH-B -- MTU1500 1,000 Mbps IPv4
Netnod Stockholm GREEN -- MTU1500: STH-A -- MTU1500 1,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 AS49769 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS49769 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 191 668
v4
AS6939 HURRICANE 30 107
v4
AS25091 IP-Max 15 98
v4
AS8434 34 90
v4
AS33891 CORE-BACKBONE 10 33
v4
AS5405 7 26
v4
AS20764 RASCOM-AS 6 24
v4
AS39351 ESAB-AS 4 16
v4
AS4455 3 15
v4
AS12552 2 14
v4
AS50304 4 13
v4
AS35280 F5 4 12
v4
AS13194 BITE 1 3
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS49769 in AS paths

Observed downstreams
Families
AS213195 30 276
v4

No rows match “”.

Showing of

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 99
v4
AS49544 i3Dnet 2 18
v4
AS42473 2 9
v4
AS42541 2 9
v4
AS199524 GCORE 2 9
v4
AS213195 1 6
v4
AS35598 1 3
v4
AS36236 NETACTUATE 1 3
v4
AS205206 Netsite 1 3
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.