So 1.1.1.0/24 doesn't seem to be in the global table from North American carrier perspectives. It's certainly not a routed prefix for any of my machines in Nor

So 1.1.1.0/24 doesn't seem to be in the global table from North American carrier perspectives. It's certainly not a routed prefix for any of my machines in North America. The closest prefix I can see an announcement for on a global basis is 1.1.3.0/24 (CHINANET FUJIAN PROVINCE NETWORK). Like bcoates said, there's a bunch of dumb stuff out there designed by people who barely understood TCP/IP and used non-RFC1918 ranges for customer equipment. Occasionally they leak indirectly into a table that's being redistributed into some mom and pop ISP's BGP announcements, and this happens. The backbone carriers of the Internet all (well, maybe not tata) have much stronger filters than Honest Achmed's used car sales and Internet transit, so they tend to leak only within a country or region. Occasionally its some ISP internal services and it's done deliberately to have easy to remember IP addresses for techs working on the network. I mean, do you want to have to remember to point SNMP traps to 216.31.49.167 or would you rather only have to remember 1.1.1.1 instead? Then the prefix hits the border bogon filter and remains entirely with that ISP's network. Now that I think about it, scanning ISPs for known unannounced prefixes in the global table would be kind of a fun project to discover all the little internal services ISPs might have squirreled away throughout their network.