Skip to main content

AS199325

SEMPLIFY

Server Engineering Manager

Registry

Authoritative registration data

AS number
199325
Name
SEMPLIFY
Organisation
Server Engineering Manager
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS199325
185.21.116.0/24 IPv4 /24 not checked
185.21.117.0/24 IPv4 /24 not checked
185.21.118.0/24 IPv4 /24 not checked
185.21.119.0/24 IPv4 /24 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 AS199325
Address families
MIX-IT 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS199325 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 143 651
v4
AS6762 SEABONE-NET 120 518
v4
AS8218 NEO-ASN 5 39
v4
AS29075 IELO 3 9
v4
AS4455 BSO 2 9
v4
AS24961 MYLOC-AS 2 6
v4
AS6204 ZET-NET 1 3
v4
AS60171 AFRIX-AS 1 3
v4
AS137409 GSLNETWORKS-AS-AP 1 3
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS199325 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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