Skip to main content

AS39101

PITEL

Piter-telecom Ltd.

Registry

Authoritative registration data

AS number
39101
Name
PITEL
Organisation
Piter-telecom Ltd.
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 AS39101
80.254.16.0/20 IPv4 /20 not checked
80.254.16.0/21 IPv4 /21 not checked
185.250.128.0/22 IPv4 /22 not checked
185.250.128.0/23 IPv4 /23 not checked
185.250.130.0/23 IPv4 /23 not checked
185.250.128.0/24 IPv4 /24 not checked
80.254.17.0/24 IPv4 /24 not checked
80.254.19.0/24 IPv4 /24 not checked
80.254.23.0/24 IPv4 /24 not checked
2a00:cd00::/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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS39101 in AS paths

Observed upstreams
Families
AS31500 GNM-AS 305 2,031
v4 v6
AS31133 MF-MGSM-AS 264 448
v4
AS207056 BONCH-IT 58 354
v4
AS3216 SOVAM-AS 118 318
v4
AS6939 HURRICANE 70 207
v4 v6
AS41327 FIBERTELECOM-AS 2 17
v4 v6
AS60171 AFRIX-AS 1 9
v4 v6
AS15958 CETIN_doo_AS 1 8
v4
AS25091 IP-Max 4 7
v4
AS9198 KAZTELECOM-AS 1 1
v4
AS43727 KVANT-TELECOM 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS39101 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.