The "database computer code" they are talking about is not the actual database software (e.g. oracle, postgres, or whatever). It's the proprietary code used to

The "database computer code" they are talking about is not the actual database software (e.g. oracle, postgres, or whatever). It's the proprietary code used to keep the data in the database accurate, up to date, distributed, etc. And the code used for communicating with the service providers, co-ops, LSMSs, etc. This may seem a small thing and may be somewhat conceptually similar to DNS. But in reality it is an entire ecosystem of it's own with complexities that are not readily apparent. The incumbent (Neustar) has no obligation to share it's IP with Telcordia. "The database is significant because it tracks nearly every phone number in North America, making it a key tool for law enforcement agencies seeking to monitor criminal or espionage targets." This statement is potentially very misleading. The NPAC does not "live" route telephone calls. The NPAC is the database of ported phone number and various characteristics about them. The database is replicated to LSMS databases at the service providers. When you make a call it does not route through the NPAC. It routes through the service providers, period. While the NPAC could be helpful to law enforcement for knowing which SP manages a particular number and various other characteristics about that number, it would not be helpful as some sort of one-stop shop for wire tapping. From the NPAC site: "LSMS (Local Service Management System): The system owned by a service provider and which receives data broadcast from the NPAC/SMS. The LSMS provisions the service provider's downstream systems, such as its LNP call routing database. The LSMS is a mechanized system used (primarily) to receive data broadcasts from the NPAC/SMS."