NO_ZIPLINE_ENDPOINT_VIA_ETHERNET
Applicable alarms (1)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”The Zipline cloud endpoint can’t be reached from the dock. This is detected on the dock when pings to ping.platform.flyzipline.com fail for >30 seconds.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-the-dock-reporting-no-internet-via-e{"<small><b>Step 1</b></small><br/>Question: Is the dock reporting NO_INTERNET_VI..."}
reference-no-internet-via-ethernet("<small><b>Step 2</b></small><br/>Reference: Reference NO_INTERNET_VIA_ETHERNET...")
check-the-dns-resolution-speeds["<small><b>Step 3</b></small><br/>Action: Check the DNS resolution speeds SSH i..."]
is-the-time-more-than-2-seconds{"<small><b>Step 4</b></small><br/>Question: Is the time more than 2 seconds? !..."}
check-site-port-link-status{"<small><b>Step 5</b></small><br/>Question: On FleetWrangler, check if both site ..."}
escalate-to-it-networking-oncall{{"<small><b>Step 6</b></small><br/>Escalation: Escalate to IT Networking On Call in ..."}}
escalate-to-p2-dock-hardware-on-call{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Dock Hardware On Call...."}}
since-this-is-not-a-site-problem-or-a-d{{"<small><b>Step 8</b></small><br/>Escalation: Since this is not a site problem or a..."}}
is-the-dock-reporting-no-internet-via-e -->|Yes| reference-no-internet-via-ethernet
is-the-dock-reporting-no-internet-via-e -->|No| check-the-dns-resolution-speeds
check-the-dns-resolution-speeds --> is-the-time-more-than-2-seconds
is-the-time-more-than-2-seconds -->|Yes| check-site-port-link-status
is-the-time-more-than-2-seconds -->|No| since-this-is-not-a-site-problem-or-a-d
check-site-port-link-status -->|Yes| escalate-to-it-networking-oncall
check-site-port-link-status -->|No| escalate-to-p2-dock-hardware-on-call
style is-the-dock-reporting-no-internet-via-e fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style reference-no-internet-via-ethernet fill:#f3e8ff,stroke:#a855f7,color:#581c87
style check-the-dns-resolution-speeds fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-time-more-than-2-seconds fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style check-site-port-link-status fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-it-networking-oncall fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-p2-dock-hardware-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style since-this-is-not-a-site-problem-or-a-d fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
NO_INTERNET_VIA_ETHERNET alarm?
Ethernet Port 1: LINK_STATUS_DOWN 0 bytes/s
Ethernet Port 2: LINK_STATUS_UP 10513052 bytes/sIs the link up?
@it-networking-oncall in Slack.Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.