Skip to main content

AS48349

ARQA-QUIK-AS

ARQA Technologies LLC

Registry

Authoritative registration data

AS number
48349
Name
ARQA-QUIK-AS
Organisation
ARQA Technologies LLC
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 AS48349
195.133.252.0/24 IPv4 /24 not checked
195.85.206.0/24 IPv4 /24 not checked
91.209.122.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 AS48349 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS48349 in AS paths

Observed upstreams
Families
AS29226 290 480
v4
AS2854 ROSPRINT-AS 185 231
v4
AS12389 159 204
v4
AS20485 114 144
v4
AS25091 IP-Max 4 8
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS48349 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4
AS20764 RASCOM-AS 1 1
v4
AS28910 1 1
v4
AS28917 1 1
v4
AS29049 1 1
v4
AS36236 NETACTUATE 1 1
v4
AS41327 FIBERTELECOM-AS 1 1
v4
AS41722 1 1
v4
AS49673 TRUENETWORK 1 1
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.