Skip to content
ipaddress.co.nz

BGP Prefix Lookup

Enter a prefix (or a single address). Answered from our daily copy of the global routing table.

Examples:

156.75.0.0/16

One collector's view (APNIC). A route filtered before it reaches that collector is not listed.

Announced exactly

  • 156.75.0.0/16AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.0.0
Registry
ARIN · United States · Dec 19, 1991
Delegated block
156.75.0.0 – 156.75.255.255

Covering routes

0

No less-specific route covers it.

More-specific routes

35 more-specifics from 1 origin AS(es)
  • 156.75.0.0/17AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.0.0
  • 156.75.0.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.0.0
  • 156.75.1.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.1.0
  • 156.75.2.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.2.0
  • 156.75.3.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.3.0
  • 156.75.5.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.5.0
  • 156.75.6.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.6.0
  • 156.75.7.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.7.0
  • 156.75.10.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.10.0
  • 156.75.13.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.13.0
  • 156.75.14.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.14.0
  • 156.75.15.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.15.0
  • 156.75.16.0/21AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.16.0
  • 156.75.20.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.20.0
  • 156.75.24.0/23AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.24.0
  • 156.75.28.0/23AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.28.0
  • 156.75.30.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.30.0
  • 156.75.64.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.64.0
  • 156.75.65.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.65.0
  • 156.75.66.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.66.0
  • 156.75.67.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.67.0
  • 156.75.68.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.68.0
  • 156.75.69.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.69.0
  • 156.75.73.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.73.0
  • 156.75.75.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.75.0
  • 156.75.128.0/18AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.128.0
  • 156.75.192.0/19AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.192.0
  • 156.75.224.0/20AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.224.0
  • 156.75.240.0/22AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.240.0
  • 156.75.244.0/23AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.244.0
  • 156.75.248.0/21AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.248.0
  • 156.75.248.0/22AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.248.0
  • 156.75.252.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.252.0
  • 156.75.253.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.253.0
  • 156.75.254.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Not found156.75.254.0

On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.0.0/14. This tool looks a prefix up in our daily copy of the global routing table and shows three things:

  • Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
  • Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
  • More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).

Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.

The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.

Frequently asked questions

Why is my /24 not listed but a /16 is?

Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.

What is a more-specific hijack?

Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.

Can I enter a single address?

Yes. The tool then shows the most specific announced route that contains it.

Related