Skip to main content

AS202548

QUADRIS

Quadris Ltd

Registry

Authoritative registration data

AS number
202548
Name
QUADRIS
Organisation
Quadris Ltd
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS202548
185.212.185.0/24 IPv4 /24 not checked
185.42.160.0/24 IPv4 /24 not checked
45.130.45.0/24 IPv4 /24 not checked
2a0f:a040::/29 IPv6 /29 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 AS202548
Address families
LINX Manchester 2,000 Mbps IPv4 · IPv6

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS202548 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 281 1,162
v4 v6
AS174 COGENT-174 37 132
v4
AS61049 EXASCALE 3 3
v6
AS4455 BSO 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS202548 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 11
v6
AS3170 VELOXSERV 1 1
v6
AS36236 NETACTUATE 1 1
v6
AS48070 DSM 1 1
v6

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.