bgpreport

Network · data from 2026-11-12

AS197862 Netfone Netfone Telecom Tavkozlesi es Szolgaltato KFT

Registry name: Netfone Netfone Telecom Tavkozlesi es Szolgaltato KFT, HU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197862, 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.
2a05:3087::/32 Valid Nonecovered by 2a05:3080::/29 161 25% 48
176.32.200.0/21 Valid RIR databaseRIPE 673 100% 67
185.6.156.0/22 Valid RIR databaseRIPE 673 100% 67
185.71.104.0/22 Valid RIR databaseRIPE 668 99% 67
2a05:3080::/29 Valid RIR databaseRIPE 627 99% 67
176.32.201.0/24 Valid RIR databaseRIPE 139 21% 43
176.32.202.0/24 Valid RIR databaseRIPE 139 21% 43
185.71.106.0/24 Valid RIR databaseRIPE 139 21% 43
185.71.107.0/24 Valid RIR databaseRIPE 139 21% 43

AS-SET

AS197862 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2a05:3087::/32No route object for it. A route object for 2a05:3080::/29 with origin AS197862 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197862 in the RIR database for the space.161 of 636

Route objects not announced

Every route object with origin AS197862 is announced.

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.