Skip to main content

AS44629

POINTUA-AS

--- ReTN ---

Registry

Authoritative registration data

AS number
44629
Name
POINTUA-AS
Organisation
--- ReTN ---
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 AS44629
176.106.192.0/19 IPv4 /19 not checked
178.212.240.0/21 IPv4 /21 not checked
195.42.130.0/23 IPv4 /23 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 AS44629
Address families
1-IX EU 10,000 Mbps IPv4
1-IX UA 10,000 Mbps IPv4
DTEL-IX: PUBLIC 10,000 Mbps IPv4
Giganet IXN: Global exchange 10,000 Mbps IPv4
LVIV-IX: Main 10,000 Mbps IPv4
UA-IX 10,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 AS44629 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS44629 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 82 207
v4
AS35297 DATALINE-AS 172 196
v4
AS50263 IXP-1-IX-EU 33 77
v4
AS6939 HURRICANE 8 15
v4
AS14840 ASN14840 2 8
v4
AS3303 SWISSCOM 1 3
v4
AS6204 ZET-NET 1 3
v4
AS6663 TTI-NET 1 2
v4
AS50629 LWLCOM 1 1
v4
AS263444 ASN263444 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS44629 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 10
v4
AS8218 NEO-ASN 1 6
v4
AS48919 UA-CITY-AS 1 3
v4
AS49544 i3Dnet 1 3
v4
AS34927 iFog-GmbH 1 2
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.