MIGO Looking Glass AS263152

Migo Internet Looking Glass

Public network diagnostic tool for AS263152. Ping, traceroute and BGP routes run on our routers; MTR, DNS, WHOIS, throughput and the rest run on this server.

Online IPv4 | 177.92.253.104 IPv6 | 2804:1784:a:200::104 BGP Route Lookup

Your IPv4 216.73.216.187

Your IPv6 not detected

Source port9746

ProtocolHTTP/1.1

HTTPSyes

TCP-MSS1448 bytes

RTT134.351 ms

Output

Via

0.0

Mbit/s

Ready

Download

—

Upload

—

Latency

—

Jitter

—

Retransmissions

—

ICMP loss

—

[LG]

Select a router, a command and a destination,

then click Run.

Network

Migo Internet (AS263152) is a Brazilian ISP present at Equinix SP2 with DDoS-protected AlwaysOn transit. 5 PoPs available.

Commands

Ping IPv4 Ping IPv6 Traceroute IPv4 Traceroute IPv6 MTR SuperPing BGP Route DNS Lookup HTTP/HTTPS Speed test IPv4 / IPv6 DNSSEC IPERF3 slot TCP probe UDP probe Path MTU WHOIS

What does each one do?

Source IPs

IPv4: 177.92.253.104
IPv6: 2804:1784:a:200::104

Routers

Migo LG Server — Barueri, SP | LG Server
Core Equinix-SP2 — Barueri, SP | Equinix SP2
Router Clementina — Clementina, SP
Router MigoPV — Pres. Venceslau, SP
Router Tupa — Tupa, SP

Peering & NOC

PeeringDB | bgp.he.net | bgp.tools
noc@migonet.com.br

Acceptable use

Limit of 10 req/min per IP. RFC1918 and private addresses are automatically blocked.

Command reference

Every test runs from this network's own vantage point unless it says otherwise, so what you see here is what our routers and our server see — not what your own machine sees.

Reachability

Ping IPv4 / IPv6: Five ICMP echoes. The first thing to try, and the first thing to distrust: plenty of hosts and firewalls drop ICMP while serving traffic perfectly. Silence here is not proof of an outage. Use it to confirm a host is alive and to read the round-trip time.
Traceroute IPv4 / IPv6: Shows each hop on the way and the ASN behind it. Latency that climbs and stays high marks where the distance is; latency that spikes on one hop and drops again is usually that router deprioritising its own replies, not a problem for traffic passing through. Use it to find where a path leaves our network and whose network it enters.
MTR: Traceroute and ping combined over ten cycles, with loss and latency per hop. Loss that appears at one hop and disappears further along is cosmetic. Loss that starts at a hop and continues to the destination is real. Use it when a path is slow or lossy and you need to say which hop owns the problem.
SuperPing: One hundred packets in quick succession, reporting loss, latency and jitter. Packet size is adjustable and the DF bit is set by default, so an oversized packet reports a fragmentation error instead of silently being split. Use it for jitter — the enemy of voice and gaming — and to probe how large a packet survives the path.
Path MTU: Binary search for the largest packet that crosses without fragmenting. 1500 means a clean Ethernet path; 1492 is typical of PPPoE; anything below 1400 usually means a tunnel. Use it when large transfers stall while small requests work — the classic signature of a broken MTU with PMTU discovery blocked.

Routing

BGP Route: How our routers reach a prefix: AS path, communities, preference and validation state. Prefixes inside our own space are shown as their covering aggregate — internal links are not published here. Use it to see which upstream carries a destination, and to confirm a prefix is visible from our table at all.
WHOIS: Origin ASN, organisation, RIR, allocation date, geolocation, RPKI status and IRR objects, in one answer. RPKI is the part worth reading: valid means a signed ROA authorises that AS to announce that prefix, invalid means somebody is announcing what they should not, and not found means nothing was published either way. Use it before accepting a prefix from a peer, or when a customer reports being blocked.

Name resolution

DNS Lookup: A and AAAA from each of our resolvers, plus NS, MX, TXT, CAA and SOA, and the DNSSEC flag. Give it an address instead and it returns the PTR and checks whether that name resolves back to the same address. Use it when resolvers disagree, and for the forward-confirmed reverse check that mail servers demand.
DNSSEC: Give it a domain and it reports whether the zone is signed and whether validation succeeds. Give it a resolver address and it tests that resolver instead: a validating one refuses a deliberately broken name and marks good answers as authenticated. Use it to prove a resolver protects its users, or to find out why a signed domain fails to resolve for some people and not others.

Transport and applications

TCP probe: Opens the handshake five times against a chosen port and reports the time, the spread and whether the port is open, closed or filtered. Ports are limited to a published list. Use it to separate "the service is down" from "the network cannot reach it" — a refused connection and a timeout mean different things.
UDP probe: Response time, jitter and loss against DNS or NTP. UDP has no handshake, so only services that answer can be measured this way. Use it when a resolver or time source feels slow: UDP loss is invisible to the application, which simply waits.
HTTP/HTTPS: Status, redirect chain, certificate, and the time spent on DNS, TCP, TLS and the first byte. The IP version can be forced. Use it to place a slow page: a long DNS phase, a long handshake and a long first byte each point somewhere different.

Your own connection

Speed test: Runs in your browser, between your machine and this server, over several parallel connections. It also reports TCP retransmissions counted by the kernel and ICMP loss towards your address. Use it to measure your link to us. A result below your subscribed rate can come from Wi-Fi, from the device, or from the path — this test cannot tell them apart on its own.
IPv4 / IPv6: Opens one connection over each family from your machine and reports the address, MSS and round-trip time of each. A timeout and a refusal are reported differently: a refusal means no stack, a timeout means an address and a route exist but the packets go nowhere. Use it to find out whether IPv6 actually works where you are, which is rarely the same question as whether you have an IPv6 address.
IPERF3 slot: Opens a temporary listener on a random high port for a few minutes, accepting one test. You run the iperf3 client yourself; the commands are printed for you. Use it when a browser is not enough: real UDP throughput, sustained multi-stream TCP, and the numbers other operators will accept.

Reading the results

Jitter matters more than latency: A steady 80 ms carries a call comfortably. An average of 30 ms that swings between 5 and 200 does not. Look at the spread, not the mean.
Loss below 1% is not noise: TCP treats loss as congestion and slows down. A path losing 2% can feel broken while every ping still answers.
One test proves little: Before concluding, try the same destination from another router, and another destination from the same router. Two results that disagree tell you where the problem is not.