bgpreport

Network · data from 2026-11-12

AS219224 Neonhost Datacenter LTDA

Registry name: NEONHOST-DATACENTER Neonhost Datacenter LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219224, 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.
82.21.8.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a0c:b641:e20::/48 Valid Nonecovered by 2a0c:b641:e20::/44 631 99% 69
45.135.225.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
2a0c:b641:e20::/44 Valid RIR databaseRIPE 2 0%low visibility 1
2a0c:b641:e21::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS219224: RIPE::AS219224:AS-NEONHOST. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS219224 isn't in the set, or no route object for AS219224 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS219224 in itNot covered
RIPE::AS219224:AS-NEONHOST RIPE 010 No 5

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

  • ROA: origin1
  • Route object: none2
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: origin82.21.8.0/24ROAs covering it name AS834, not AS219224. If AS219224 should announce it, add a ROA for AS219224.2 of 673
Route object: none82.21.8.0/24Route objects for it name AS834. Add a route object with origin AS219224 in the RIR database for the space.2 of 673
Route object: none2a0c:b641:e20::/48No route object for it. A route object for 2a0c:b641:e20::/44 with origin AS219224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219224 in the RIR database for the space.631 of 636
AS-SET: own ASNRIPE::AS219224:AS-NEONHOSTAS219224 isn't in AS219224:AS-NEONHOST (RIPE) once expanded. Add AS219224 to it.

Route objects not announced

Every route object with origin AS219224 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.