<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://www.packet-dojo.com</loc>
<changefreq>weekly</changefreq>
<priority>1</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/pricing</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/start</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/prepare</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/interviews</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/network-troubleshooting</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/bgp-interview-questions</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/ospf-interview-questions</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/networking-interview-questions</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/network-engineer-interview</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/ccna-practice</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/ccnp-practice</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/bgp-labs</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/ospf-labs</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/network-automation</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-unreachable-branch</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-neighbor-gone-quiet</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-silent-peering</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/green-links-broken-checkout</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-route-to-nowhere</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/going-in-circles</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-missing-way-home</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-little-too-quiet</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/everyone-is-a-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-prefix-without-a-voice</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/warehouse-scanners-offline</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-forgotten-subnet</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/after-the-cleanup-window</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-branch-left-behind</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-overnight-discard</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-route-with-no-exit</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-disappearing-packets</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/an-overzealous-aggregate</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-transit-detour</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-wrong-turn</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-circular-dependency</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/two-routers-no-progress</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/requests-without-replies</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/half-a-connection</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-side-blind-spot</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-one-way-change</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-backbone-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-isolated-service-leaf</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/lost-after-an-area-change</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/same-subnet-different-worlds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/hardening-gone-sideways</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/an-empty-neighbor-table</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-quiet-transit</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/no-hello-from-the-core</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/connected-never-advertised</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-missing-service-lsa</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/neighbors-are-not-enough</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-unannounced-network</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-onboarding-typo</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/who-is-on-the-other-end</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/peering-after-the-migration</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-mismatched-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-service-nobody-learned</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-healthy-but-empty-peer</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/origination-after-the-move</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-connected-prefix-stays-local</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-payment-gateway-lockout</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-overly-broad-deny</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-secure-but-unavailable-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/restore-access-preserve-isolation</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/one-host-disappears-inside-a-healthy-subnet</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/half-a-subnet-takes-a-circular-detour</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-new-application-host-is-outside-the-route</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/requests-arrive-but-the-client-never-hears-back</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-second-client-subnet-was-left-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/ospf-is-healthy-but-a-host-still-vanishes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-valid-bgp-prefix-with-a-hidden-forwarding-trap</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-application-is-sent-to-the-telemetry-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-second-application-loops-at-the-core</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/one-repair-is-not-enough-after-the-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/only-one-client-address-can-receive-replies</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-summary-route-hides-a-missing-service-prefix</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/one-connected-subnet-never-entered-ospf</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-telemetry-hardening-change-stopped-routing</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/only-one-side-of-the-branch-area-changed</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-advertised-network-misses-the-actual-loopback</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/neighbors-recover-but-the-application-does-not</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-telemetry-peer-expects-the-wrong-as</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-second-service-was-never-originated</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/peering-and-forwarding-both-need-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/bgp-origination-has-the-wrong-prefix-length</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-telemetry-prefix-was-mistyped-at-origination</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/a-permit-exists-but-an-earlier-rule-wins</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-policy-is-correct-on-the-wrong-interface</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-right-port-with-the-wrong-transport</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-lower-half-of-the-client-subnet-works</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-lower-half-of-the-service-subnet-works</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/the-reverse-path-has-its-own-security-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/one-dns-transport-path-is-missing</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/restore-two-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-the-primary-service-is-unreachable</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-traffic-returns-to-the-client-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-one-service-address-drops-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-only-the-upper-half-responds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-the-second-client-subnet-gets-no-reply</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-both-services-fail-after-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-one-subnet-is-absent-from-the-routing-domain</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-the-service-edge-loses-its-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-hardening-interrupts-service-reachability</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-a-healthy-control-plane-hides-a-dropped-host</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-neighbor-recovery-is-only-the-first-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-the-service-edge-stops-exchanging-bgp-routes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-a-new-service-prefix-never-reaches-clients</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-the-advertised-prefix-does-not-match-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-export-recovery-leaves-a-return-path-failure</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-the-permit-rule-is-present-but-traffic-fails</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-new-client-addresses-cannot-use-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-the-new-service-host-fails-its-network-check</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-the-port-is-open-for-the-wrong-traffic</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/campus-restore-both-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-the-primary-service-is-unreachable</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-traffic-returns-to-the-client-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-one-service-address-drops-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-only-the-upper-half-responds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-the-second-client-subnet-gets-no-reply</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-both-services-fail-after-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-one-subnet-is-absent-from-the-routing-domain</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-the-service-edge-loses-its-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-hardening-interrupts-service-reachability</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-a-healthy-control-plane-hides-a-dropped-host</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-neighbor-recovery-is-only-the-first-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-the-service-edge-stops-exchanging-bgp-routes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-a-new-service-prefix-never-reaches-clients</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-the-advertised-prefix-does-not-match-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-export-recovery-leaves-a-return-path-failure</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-the-permit-rule-is-present-but-traffic-fails</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-new-client-addresses-cannot-use-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-the-new-service-host-fails-its-network-check</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-the-port-is-open-for-the-wrong-traffic</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/branch-wan-restore-both-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-the-primary-service-is-unreachable</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-traffic-returns-to-the-client-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-one-service-address-drops-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-only-the-upper-half-responds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-the-second-client-subnet-gets-no-reply</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-both-services-fail-after-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-one-subnet-is-absent-from-the-routing-domain</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-the-service-edge-loses-its-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-hardening-interrupts-service-reachability</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-a-healthy-control-plane-hides-a-dropped-host</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-neighbor-recovery-is-only-the-first-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-the-service-edge-stops-exchanging-bgp-routes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-a-new-service-prefix-never-reaches-clients</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-the-advertised-prefix-does-not-match-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-export-recovery-leaves-a-return-path-failure</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-the-permit-rule-is-present-but-traffic-fails</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-new-client-addresses-cannot-use-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-the-new-service-host-fails-its-network-check</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-the-port-is-open-for-the-wrong-traffic</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/data-center-restore-both-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-the-primary-service-is-unreachable</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-traffic-returns-to-the-client-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-one-service-address-drops-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-only-the-upper-half-responds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-the-second-client-subnet-gets-no-reply</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-both-services-fail-after-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-one-subnet-is-absent-from-the-routing-domain</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-the-service-edge-loses-its-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-hardening-interrupts-service-reachability</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-a-healthy-control-plane-hides-a-dropped-host</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-neighbor-recovery-is-only-the-first-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-the-service-edge-stops-exchanging-bgp-routes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-a-new-service-prefix-never-reaches-clients</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-the-advertised-prefix-does-not-match-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-export-recovery-leaves-a-return-path-failure</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-the-permit-rule-is-present-but-traffic-fails</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-new-client-addresses-cannot-use-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-the-new-service-host-fails-its-network-check</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-the-port-is-open-for-the-wrong-traffic</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/regional-operations-restore-both-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-the-primary-service-is-unreachable</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-traffic-returns-to-the-client-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-one-service-address-drops-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-only-the-upper-half-responds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-the-second-client-subnet-gets-no-reply</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-both-services-fail-after-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-one-subnet-is-absent-from-the-routing-domain</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-the-service-edge-loses-its-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-hardening-interrupts-service-reachability</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-a-healthy-control-plane-hides-a-dropped-host</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-neighbor-recovery-is-only-the-first-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-the-service-edge-stops-exchanging-bgp-routes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-a-new-service-prefix-never-reaches-clients</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-the-advertised-prefix-does-not-match-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-export-recovery-leaves-a-return-path-failure</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-the-permit-rule-is-present-but-traffic-fails</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-new-client-addresses-cannot-use-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-the-new-service-host-fails-its-network-check</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-the-port-is-open-for-the-wrong-traffic</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/service-edge-restore-both-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-the-primary-service-is-unreachable</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-traffic-returns-to-the-client-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-one-service-address-drops-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-only-the-upper-half-responds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-the-second-client-subnet-gets-no-reply</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-both-services-fail-after-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-one-subnet-is-absent-from-the-routing-domain</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-the-service-edge-loses-its-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-hardening-interrupts-service-reachability</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-a-healthy-control-plane-hides-a-dropped-host</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-neighbor-recovery-is-only-the-first-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-the-service-edge-stops-exchanging-bgp-routes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-a-new-service-prefix-never-reaches-clients</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-the-advertised-prefix-does-not-match-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-export-recovery-leaves-a-return-path-failure</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-the-permit-rule-is-present-but-traffic-fails</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-new-client-addresses-cannot-use-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-the-new-service-host-fails-its-network-check</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-the-port-is-open-for-the-wrong-traffic</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/backup-network-restore-both-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-the-primary-service-is-unreachable</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-traffic-returns-to-the-client-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-one-service-address-drops-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-only-the-upper-half-responds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-the-second-client-subnet-gets-no-reply</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-both-services-fail-after-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-one-subnet-is-absent-from-the-routing-domain</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-the-service-edge-loses-its-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-hardening-interrupts-service-reachability</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-a-healthy-control-plane-hides-a-dropped-host</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-neighbor-recovery-is-only-the-first-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-the-service-edge-stops-exchanging-bgp-routes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-a-new-service-prefix-never-reaches-clients</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-the-advertised-prefix-does-not-match-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-export-recovery-leaves-a-return-path-failure</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-the-permit-rule-is-present-but-traffic-fails</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-new-client-addresses-cannot-use-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-the-new-service-host-fails-its-network-check</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-the-port-is-open-for-the-wrong-traffic</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/industrial-campus-restore-both-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-the-primary-service-is-unreachable</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-traffic-returns-to-the-client-edge</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-one-service-address-drops-out</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-only-the-upper-half-responds</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-the-second-client-subnet-gets-no-reply</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-both-services-fail-after-route-cleanup</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-one-subnet-is-absent-from-the-routing-domain</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-the-service-edge-loses-its-neighbor</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-hardening-interrupts-service-reachability</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-a-healthy-control-plane-hides-a-dropped-host</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-neighbor-recovery-is-only-the-first-repair</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-the-service-edge-stops-exchanging-bgp-routes</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-a-new-service-prefix-never-reaches-clients</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-the-advertised-prefix-does-not-match-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-export-recovery-leaves-a-return-path-failure</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-the-permit-rule-is-present-but-traffic-fails</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-new-client-addresses-cannot-use-the-service</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-the-new-service-host-fails-its-network-check</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-the-port-is-open-for-the-wrong-traffic</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/challenges/remote-access-restore-both-services-without-opening-the-boundary</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/hetzner-2026</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/azure-westus-2026</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/rcom-2026</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cloudflare-byoip-2026</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cloudflare-miami-2026</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cantv-2026</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/optus-triple-zero-2025</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/bart-2025-09</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cloudflare-1111-2025</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/voxility-2025</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/north-korea-roa-2025</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/upx-2025</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/otc-attribute-2025</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/uztelecom-2024</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/azure-front-door-2024-07</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/azure-central-us-2024</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/eletronet-2024</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/att-mobility-2024</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/ams-ix-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/optus-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/att-911-testing-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/github-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/juniper-attribute-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/angola-cables-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/tic-armenia-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/tim-italy-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/microsoft-wan-2023</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/verizon-volte-911-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/celer-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/rostelecom-apple-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/rogers-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/kddi-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/mikrotik-prepend-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cloudflare-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/ams-ix-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/rtcomm-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/klayswap-2022</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/kt-2021</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/ovh-2021</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/telia-2021</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/facebook-2021</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/vodafone-idea-2021</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/georgia-tech-2021</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cablevision-2021</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/myanmar-2021</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/georgia-tech-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/telstra-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/centurylink-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/premier-dc-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/tulix-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/conecte-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cloudflare-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/tmobile-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/ibm-cloud-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/rostelecom-2020</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/verizon-dqe-2019</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/safehost-2019</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/twnic-2019</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/mainone-2018</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/google-cloud-2018</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/iran-tci-2018</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/bitcanal-2018</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/payment-processors-2018</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cloudflare-gatebot-2018</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/enet-route53-2018</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/nhs-wales-2018</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/dvlink-2017</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/level3-2017</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/infovale-2017</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/google-verizon-2017</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/wannacry-nhs-2017</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/rostelecom-2017</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/att-volte-911-2017</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/iran-tic-2017</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/backconnect-2016</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/census-2016</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/google-cloud-2016-08</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/southwest-2016</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/telia-2016</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/innofield-2016</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/gce-2016</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/china-telecom-verizon-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/bharti-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/axcelx-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/telekom-malaysia-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/ams-ix-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/gce-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/enzu-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/hathway-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/vega-2015</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/syria-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/internexa-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/volumedrive-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/twc-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/stack-exchange-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/512k-day-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/indosat-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/turk-telekom-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/canadian-isp-2014</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/aws-sa-east-1-2013</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/hacking-team-2013</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/iceland-2013</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cb3rob-2013</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cloudflare-flowspec-2013</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/belarus-2013</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/avenir-2012</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/moratel-2012</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/dery-2012</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/fog-creek-2012</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/dodo-telstra-2012</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/etsy-2012</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/f-root-2011</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/aws-ebs-2011</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/facebook-china-telecom-2011</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/indosat-2011</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/evolva-2010</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/anexia-2010</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/china-telecom-2010</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/faa-fti-2009</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/wind-2009</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/supronet-2009</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/ctbc-2008</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/pilosov-kapela-2008</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/youtube-pakistan-2008</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/lax-cbp-2007</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/coned-2006</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/cogent-google-2005</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/ttnet-2004</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/slammer-2003</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/beth-israel-2002</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/microsoft-dns-2001</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/uunet-1997</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/as7007-1997</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
<url>
<loc>https://www.packet-dojo.com/incidents/valve-steam</loc>
<changefreq>weekly</changefreq>
<priority>0.7</priority>
</url>
</urlset>
