ep.net status?

Anyone know what's going on with ep.net? It's been unresolvable since
at least yesterday.

PAIX, SIX and several other exchanges point to ep.net to register for
an IP assignment at the exchange.

The two authoritive servers, flag.ep.net (198.32.4.13) dot.ep.net (198.32.2.10) are not working by my testing (from own network as well as looking glasses).

I cannot even reach flag, and dot doesn't know about ep.net.

$ dig @198.32.2.10 ep.net soa

; <<>> DiG 8.1 <<>> @198.32.2.10 ep.net soa
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 10
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; ep.net, type = SOA, class = IN

$ dig @198.32.4.13 ep.net soa

; <<>> DiG 8.1 <<>> @198.32.4.13 ep.net soa
; (1 server found)
;; res options: init recurs defnam dnsrch
;; res_send to server 198.32.4.13: Connection timed out

Any insight or answer on how to register for IPs at an exchange ( since
the exchange operators are just as stumped ) would be greatly appreciated.

Thanks,
-Chris

I know Bill was previously having some firewalling issues, possibly is
again. I'd assume he'll respond to this email...

On Thu, Feb 28, 2002 at 02:39:27PM -0600, Chris Parker typed:

I can ping both NS's from LAAP attached box

I can also ping via transit inbound to AS 226

...
PAIX, SIX and several other exchanges point to ep.net to register for
an IP assignment at the exchange.
...

Actually, and for the record, PAIX gets its IP address blocks from EP.Net
but we don't use them for address allocations/registrations within those
blocks. That's handled internally here. When EP.Net receives a request
for a PAIX-handled block, they forward the request to us.