Current _spf-internal.plus.net / _spf-internal2.plus.net SPF records incomplete?

[#1]

I've recently reviewed my personal domain SPF record and switched it from using

include:madasafish.com

to

include:_spf-internal.plus.net include:_spf-internal2.plus.net

on advice found on the forums here.

I also have a DMARC record requesting that I get sent delivery summaries (rua=mailto:postmaster@[my domain]), and Google was so kind to tell me that it received legitimate, DKIM signed emails that I know I sent from IP addresses that are not in the plus.net SPF lists:

  <record>
    <row>
      <source_ip>212.227.126.135</source_ip>
      <count>1</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>fail</spf>
      </policy_evaluated>
    </row>
    <!-- snip -->
  </record>
  <record>
    <row>
      <source_ip>212.227.126.131</source_ip>
      <count>1</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>fail</spf>
      </policy_evaluated>
    </row>
    <!-- snip -->
  </record>

These were legitimate delivery attempts (signed cryptographically by my SMTP server with the correct DKIM key), but these two addresses, 212.227.126.131 and 212.227.126.135 are not listed in the plus.net spf-internal records, nor are they in the madasafish.com SPF records. Reverse DNS on these IP addresses gives me mout.kundenserver.de. for both.

Is there something misconfigured in the Plus.net relay setup?

[#2]

Odd!  Those IP addresses are registered as belonging to 1&1.

[#3]

I don't know if it's connected with this problem but my Namesco spf record used to pass testing but now it fails.

Has spf1-internal.plus.net gone off line or is my record corrupted?

[#4]

@Baldrick1 it should be _spf-internal.plus.net

[#5]

Tnaks again, @MisterW 

I'm clearly unable to see the wood for the trees! Obviously total unconnected, all is now well. Sorry to have butted in!