Locations and IPs.
Where our checks come from, and how to let them through your firewall.
Every check location, live from our servers
noc724 checks your monitors from agents in several Iranian cities and data centers, so one network's trouble isn't mistaken for your outage.
A monitor is only marked down when none of its locations can reach it. If some fail while another still gets an answer, you see a regional issue instead: no incident, no alert and no hit to your uptime.
Allow-listing.
If monitoring works well for you, there's nothing to do. If you get false alarms, the usual cause is a firewall or hosting provider blocking our checks. More on false alarms.
Our agents' outgoing addresses aren't fixed - they move as we add capacity - so we don't publish a list that would go stale. If your firewall only lets known addresses in, contact us and we'll help you set it up, or run a private location inside your own network - it only needs outgoing HTTPS.
Locations.
Qom
- location
- auto
- city
- Qom
- status
- online
Arvan Simin (Tehran)
- location
- tehranarvan
- city
- Tehran
- status
- online
Arvan Bamdad (Tehran)
- location
- arvan-bamdad
- city
- Tehran
- status
- online
Arvan Forough (Tehran)
- location
- arvan-forough
- city
- Tehran
- status
- online
Arvan Qeysar (Ahvaz)
- location
- abrak-ahvaz
- city
- Ahvaz
- status
- offline
Arvan Shahriar (Tabriz)
- location
- abrak-tabriz
- city
- Tabriz
- status
- offline
Tips for letting our checks through your firewall.
1. Windows Defender Firewall
- Open Windows Defender Firewall with Advanced Security.
- Click Inbound Rules › New Rule.
- Choose Custom as the rule type and click Next.
- On the Scope step, under Remote IP address, select These IP addresses and click Add.
- Enter the monitoring addresses and click OK.
- Finish the wizard to create the rule.
Official documentation:
2. Linux iptables
- Open a terminal on the server.
- Run this for each address:
sudo iptables -A INPUT -s [IP_ADDRESS] -j ACCEPT - Save the iptables rules so they survive a reboot.
Official documentation:
3. Linux UFW (Uncomplicated Firewall)
- Open a terminal on the server.
- Run:
sudo ufw allow from [IP_ADDRESS] - Reload UFW to apply it:
sudo ufw reload
Official documentation:
4. Cisco ASA Firewall
- Sign in to Cisco ASDM or the CLI.
- Go to Configuration › Firewall › Access Rules.
- Add a rule that permits traffic from the monitoring addresses to your server.
- Apply and save the configuration.
Official documentation:
5. Palo Alto Networks Firewall
- Sign in to the Palo Alto Networks web interface.
- Go to Policies › Security.
- Click Add to create a rule.
- On the Source tab, add the monitoring addresses.
- Set the rest of the rule and click OK.
- Commit the changes.
Official documentation:
6. Fortinet FortiGate Firewall
- Sign in to the FortiGate web interface.
- Go to Policy & Objects › Addresses and create an address for the monitoring IPs.
- Open Firewall Policy and create a policy that allows traffic from that address to your network.
- Move the policy to the right place in the order and save.
Official documentation:
7. Check Point Firewall
- Open SmartConsole and connect to your management server.
- Go to Security Policies.
- Add a rule that allows traffic from the monitoring addresses to your resources.
- Install the policy to apply it.
Official documentation:
8. SonicWall Firewall
- Sign in to the SonicWall web interface.
- Go to Rules › Access Rules.
- Click Add to create a rule that allows the monitoring addresses.
- Set the remaining options and save.