Skip to main content

FAQs About Augury's Network

Updated over 4 months ago

What ports must be open so that data can be sent to the Augury servers?

Transmission control protocol (TCP) and user datagram protocol (UDP) enable different types of data transmission. TCP is more reliable, while UDP prioritizes speed and efficiency.

Protocol and Port

Destination

Description

TCP 443

iot.augury.com (52.177.239.125)

api.augury.com

IoT services

TCP 8883 (443 on customer request)

production-iothub.azure-devices.net

20.80.227.212

IoT data transfer

TCP/UDP 655

35.227.38.87

35.227.23.164

35.197.254.125

35.197.217.254

35.189.119.102

35.196.166.158

SupportService

UDP/TCP 123

0.pool.ntp.org

1.pool.ntp.org

2.pool.ntp.org

3.pool.ntp.orgor

Customer-provided (local NTP server or time.google.com)

NTP

How many endpoints and nodes are required?

The number of Endpoints and Nodes is determined by our site survey performed as preparation for the attachment of the devices.

The endpoint searches for the nearest working node, with wireless coverage typically up to 17 m or 50 ft, but can be greater depending on the environment.

How often does the sensor send data to the node?

Augury samples the data from a machine at least once an hour. Each endpoint transfers up to 750 KB of data per hour, and the data transfers are spread over the hour.

What’s the minimum bandwidth required?

  • The minimum bandwidth is 2 Mbps for both download and upload.

  • The Augury machine (for example, motor, gearbox, and driven component) needs about 3 MB per hour.

  • Example with 50 Augury Machines:~3.0 MB per hour per machine * 50 machines = ~150 MB per hour

  • Example for a site with 5 Mbps bandwidth and 50 machines 5 Mbps = 0.625 MBps = 2250 MB per hour

  • Augury will consume 150 MB of the available 2250 MB each hour, or ~6% of the bandwidth

  • If we send all data across in the first 15 minutes of the hour, we consume ~27% of the bandwidth.

How secure is the data transfer?

Augury is ISO 27001, ISO 9001, GDPR, and CCPA Compliant.

We have a secure-by-design approach and a low-ricks, isolated architecture.

Data is encrypted in transit and at rest.

We have device-initiated outbound connections and OTA updates to keep devices secure.

We have a multi-tenant SaaS platform with Data segregation per data classification.

We do periodic penetration testing to ensure secure environments.

Did this answer your question?