Web verification broke

keybase is claiming that my web site signature broke, but it's not clear why. Web server logs indicate "200" responses to the keybase bot, and gpg is able to validate the signature:

$ curl -s https://noah.meyerhans.us/keybase.txt | gpg --verify
gpg: Signature made Mon 12 Jan 2015 10:35:51 AM PST
gpg:                using RSA key 0xF630F3D2F5AB5DD3
gpg: Good signature from "Noah Meyerhans <frodo@morgul.net>"
gpg:                 aka "Noah Meyerhans <noahm@debian.org>"
Primary key fingerprint: A4D1 9E6E D3C1 331E F253  EA25 1CD8 D854 FE42 52C1
     Subkey fingerprint: 68F7 5D49 0E79 E993 622A  A88C F630 F3D2 F5AB 5DD3

It is possible that this is related to an expiration date on this subkey. The key's original expiration date has passed, but I've reissued the key with a newer date in the future. If keybase is still using the old key, then that could explain the failure. I have updated the public key via the keybase UI, which I expected to have solved this issue.

Start by rerunning the reported curl and gpg verification for https://noah.meyerhans.us/keybase.txt, then compare the signature and expiration data with the public key currently published through the Keybase UI. Done means identifying why Keybase rejects the web verification and confirming that the relevant key or expiration state verifies successfully.