Skip to main content

AS49551

TELESETI-AS

Teleseti Ltd

Registry

Authoritative registration data

AS number
49551
Name
TELESETI-AS
Organisation
Teleseti Ltd
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

13

IPv6 prefixes

0

Total announced

13

Announced prefixes

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

Prefixes announced by AS49551
31.148.8.0/22 IPv4 /22 not checked
91.214.220.0/22 IPv4 /22 not checked
93.171.44.0/22 IPv4 /22 not checked
31.148.10.0/23 IPv4 /23 not checked
31.148.8.0/23 IPv4 /23 not checked
91.214.220.0/23 IPv4 /23 not checked
91.214.222.0/23 IPv4 /23 not checked
93.171.44.0/23 IPv4 /23 not checked
93.171.46.0/23 IPv4 /23 not checked
31.148.10.0/24 IPv4 /24 not checked
93.171.45.0/24 IPv4 /24 not checked
93.171.46.0/24 IPv4 /24 not checked
93.171.47.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS49551 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS49551 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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