Skip to main content

AS59953

PUREFIBRE-AS

customers

Registry

Authoritative registration data

AS number
59953
Name
PUREFIBRE-AS
Organisation
customers
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 AS59953
91.109.232.0/21 IPv4 /21 not checked
185.248.220.0/22 IPv4 /22 not checked
185.78.8.0/22 IPv4 /22 not checked
2a0d:f280::/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 AS59953
Address families
LONAP: LON0 10,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 AS59953 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS59953 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 248 1,187
v4 v6
AS174 COGENT-174 44 170
v4 v6
AS8218 NEO-ASN 3 36
v4 v6
AS39351 ESAB-AS 2 8
v4 v6
AS6204 ZET-NET 1 3
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS59953 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

15 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 36
v4 v6
AS48185 team_blue 1 12
v4 v6
AS25160 VORBOSS 1 8
v4 v6
AS49544 i3Dnet 1 8
v4 v6
AS917 MISAKA 1 4
v4 v6
AS3170 VELOXSERV 1 4
v4 v6
AS31742 SOTACONNECT 1 4
v4 v6
AS34927 iFog-GmbH 1 4
v4 v6
AS35266 EXN-AS 1 4
v4 v6
AS36236 NETACTUATE 1 4
v4 v6
AS39122 BLACKNIGHT-AS 1 4
v4 v6
AS48070 DSM 1 4
v4 v6
AS50300 CUSTDC 1 4
v4 v6
AS28792 PUBLIC-INTERNET 1 3
v4
AS31122 DIGIWEB-AS 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.