bgpreport

Network · data from 2026-11-12

AS400509 ASIPFB - IPFB LLC

Registry name: ASIPFB - IPFB LLC, US · not in PeeringDB

3IPv4 routes 33.3% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS400509, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS400509, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
23.133.88.0/24 No ROA RIR databaseARIN 671 100% 67
207.174.28.0/24 No ROA RIR databaseARIN 671 100% 67
2606:bbc0::/48 No ROA RIR databaseARIN 605 95% 67
74.112.101.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS400509 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 9 are in fix.csv.

  • ROA: none3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none23.133.88.0/24No ROA covers it. Add a ROA for AS400509, maxLength 24.671 of 673
ROA: none207.174.28.0/24No ROA covers it. Add a ROA for AS400509, maxLength 24.671 of 673
ROA: none2606:bbc0::/48No ROA covers it. Add a ROA for AS400509, maxLength 48.605 of 636

Route objects not announced

Route objects with origin AS400509 whose prefix no peer sees AS400509 announce. Many are kept on purpose (backup routes, space announced only in some places).

74.112.100.0/24ARINValid
74.112.102.0/24ARINValid
74.112.103.0/24ARINValid
207.174.28.0/22ARINNo ROA
207.174.29.0/24ARINNo ROA
207.174.30.0/24ARINNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.