Skip to main content

AS42755

DATAFIBER

--------------------------------------------------------------

Registry

Authoritative registration data

AS number
42755
Name
DATAFIBER
Organisation
--------------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

2

Total announced

11

Announced prefixes

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

Prefixes announced by AS42755
46.21.160.0/20 IPv4 /20 not checked
185.138.208.0/22 IPv4 /22 not checked
91.196.168.0/22 IPv4 /22 not checked
195.184.64.0/23 IPv4 /23 not checked
91.195.200.0/23 IPv4 /23 not checked
149.12.244.0/24 IPv4 /24 not checked
91.198.27.0/24 IPv4 /24 not checked
91.199.206.0/24 IPv4 /24 not checked
91.213.112.0/24 IPv4 /24 not checked
2a02:27f8::/32 IPv6 /32 RPKI valid
2a02:27f9::/32 IPv6 /32 RPKI valid

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 AS42755
Address families
AMS-IX 20,000 Mbps IPv4 · IPv6
Frys-IX 10,000 Mbps IPv4 · IPv6
NL-ix: Main 10,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 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 AS42755 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

31 networks seen before AS42755 in AS paths

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS42755 in AS paths

Observed downstreams
Families
AS132376 BASKETASIA-AS-AP 202 325
v4 v6
AS206009 kavosnl 148 303
v4
AS51942 EKMEDIA 29 134
v4
AS202270 INFINITY 81 91
v4
AS208344 ICT-Teamwork-Continuity 48 59
v4

No rows match “”.

Showing – of

Uncertain adjacencies

30 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.