Skip to main content

AS42253

TelSP

telsp_sia

Registry

Authoritative registration data

AS number
42253
Name
TelSP
Organisation
telsp_sia
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 AS42253
193.232.214.0/23 IPv4 /23 not checked
193.232.215.0/24 IPv4 /24 not checked
193.232.216.0/24 IPv4 /24 not checked
193.232.217.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 AS42253 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS42253 in AS paths

Observed upstreams
Families
AS12389 ROSTELECOM-AS 147 561
v4
AS20764 RASCOM-AS 132 489
v4
AS28761 CrimeaCom-LLC 277 363
v4
AS25091 IP-Max 4 21
v4
AS9198 KAZTELECOM-AS 1 3
v4
AS202984 team-host 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS42253 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 18
v4
AS28910 INTAL-ASN 1 3
v4
AS37721 ORG-VTS1-AFRINIC 1 3
v4
AS49434 FBWNETWORKS 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.