Skip to content
KynexBGP

2001:43f8:1f0::/64

An exact route for 2001:43f8:1f0::/64 was found in the collector data.
Multiple origin ASNs (MOAS).2001:43f8:1f0::/64 is originated by 2 different ASNs in the collector data. This can be legitimate (anycast, migrations, DDoS protection) or a sign of a misconfiguration or hijack.

Route summary

Query2001:43f8:1f0::/64
Address familyIPv6
Matched route2001:43f8:1f0::/64
Origin AS
RPKI
  • InvalidAS37105
  • InvalidAS11845
Collector visibility3 peer session(s) at 1 collector(s)
Seen by 3 peer session(s) at 1 RouteViews collector(s). Public collectors see only part of the Internet; this is not proof of global visibility.
Last observed

Observed AS paths

CollectorCollector peerAS pathCommunitiesObserved
route-views.napafricaAS11845
2001:43f8:6d0::214
11845None
route-views.napafricaAS11845
2001:43f8:6d0::e
11845None
route-views.napafricaAS37105
2001:43f8:6d0::10:28
37105None

Collectors: route-views.napafrica

RPKI validation

PrefixOriginRPKI stateCovering ROAsValidatorChecked
2001:43f8:1f0::/64AS37105Invalid
  • 2001:43f8:1f0::/48 max /48 AS0 (AFRINIC) expires 2026-10-20
RouteViews
2001:43f8:1f0::/64AS11845Invalid
  • 2001:43f8:1f0::/48 max /48 AS0 (AFRINIC) expires 2026-10-20
RouteViews

IRR route objects

IRR objects are registrations in routing registries. Anyone with a maintainer account can create them and they are not cryptographically verified, so an IRR route object is not an RPKI authorisation.

IRRexplorer returned no route objects for this prefix.

Related prefixes

No related prefixes were returned.

External views

Data sources for this page

SourceFreshnessResultFetchedProvider observationError
RouteViews APILiveOKNone
RIPEstat Data APILiveNo recordsNot reportedNone
NLNOG IRRexplorerLiveNo recordsNot reportedNone

Page generated . See data sources and limitations.