Skip to main content

AS39083

DAVID-FROEHLICH

IT-Service David Froehlich

Registry

Authoritative registration data

AS number
39083
Name
DAVID-FROEHLICH
Organisation
IT-Service David Froehlich
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS39083
80.78.133.0/24 IPv4 /24 not checked
2a0d:2144::/40 IPv6 /40 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 AS39083
Address families
KleyReX: Peering LAN 100 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 1,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 AS39083 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS39083 in AS paths

Observed upstreams
Families
AS56382 VSERVERLTD 475 1,428
v4 v6
AS44592 SkyLink 227 618
v4 v6
AS6939 HURRICANE 175 284
v4 v6
AS44103 BAKKER-IT-AS 62 85
v4 v6
AS25091 IP-Max 7 38
v4 v6
AS14840 ASN14840 4 25
v4
AS401753 BIXCE 2 7
v4 v6
AS263444 ASN263444 2 3
v4
AS48646 STEFAN6 2 2
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS39083 in AS paths

Observed downstreams
Families
AS50801 DAVID-FROEHLICH 576 1,871
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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