bgpreport

Network · data from 2026-11-12

AS394814 ISP4LIFE - ISP4Life INC

Registry name: ISP4LIFE - ISP4Life INC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394814, 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.
2607:b480:ffff::/48 No ROA Nonecovered by 2607:b480::/32 605 95% 67
198.49.219.0/24 No ROA Other IRR onlyALTDB 2 0%low visibility 2
2607:b480::/32 No ROA RIR databaseARIN 635 100% 69
23.167.0.0/24 Valid RIR databaseARIN 673 100% 67
23.163.80.0/24 Valid RIR databaseARIN 671 100% 68
95.164.144.0/20 Valid RIR databaseRIPE 671 100% 68
95.164.200.0/22 Valid RIR databaseRIPE 671 100% 68
95.164.204.0/22 Valid RIR databaseRIPE 671 100% 68
195.225.130.0/23 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS394814 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 10 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2607:b480:ffff::/48No ROA covers it. Add a ROA for AS394814, maxLength 48.605 of 636
Route object: none2607:b480:ffff::/48No route object for it. A route object for 2607:b480::/32 with origin AS394814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394814 in the RIR database for the space.605 of 636
ROA: none198.49.219.0/24No ROA covers it. Add a ROA for AS394814, maxLength 24.2 of 673
Route object: RIR198.49.219.0/24Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
ROA: none2607:b480::/32No ROA covers it. Add a ROA for AS394814, maxLength 32.635 of 636

Route objects not announced

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

95.164.144.0/21RIPEInvalid: maxLength
95.164.152.0/22RIPEInvalid: maxLength
95.164.156.0/22RIPEInvalid: maxLength
95.164.240.0/21RIPEInvalid: origin
2001:470:584::/48ARINValid

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.