I noticed that for the "network_node" api too .. but I am very sure that this hasn't happend some time ago since the status page used that very same node_api.
Not sure what is going up or what caused this issue .. mayb you could add a ticket to the graphene repo