Skip to main content

AS204003

ORTGIES-IT

Jan-Eric Ortgies

Registry

Authoritative registration data

AS number
204003
Name
ORTGIES-IT
Organisation
Jan-Eric Ortgies
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

6

Total announced

7

Announced prefixes

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

Prefixes announced by AS204003
44.32.197.0/24 IPv4 /24 not checked
2a06:e881:5800::/46 IPv6 /46 RPKI valid
2a06:e881:5804::/46 IPv6 /46 RPKI valid
2001:67c:20ec::/48 IPv6 /48 not checked
2a06:e881:580a::/48 IPv6 /48 not checked
2a06:e881:580b::/48 IPv6 /48 not checked
2a06:e881:580c::/48 IPv6 /48 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 AS204003
Address families
Clue-IX 1,000 Mbps IPv4 · IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
FogIXP Frankfurt 1,000 Mbps IPv4 · IPv6
Frys-IX 1,000 Mbps IPv4 · IPv6
KleyReX: Peering LAN 100 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 AS204003 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS204003 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS204003 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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