bgpreport

Network · data from 2026-11-12

AS273748 L Henrique Ferreira Zoby

Registry name: AS273748 - L Henrique Ferreira Zoby, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273748, 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.
2804:8bac::/33 Invalid: maxLength Nonecovered by 2804:8bac::/32 24 4%low visibility 11
2804:8bac:8000::/33 Invalid: maxLength Nonecovered by 2804:8bac::/32 24 4%low visibility 11
38.19.59.0/24 No ROA Other IRR onlyRADB 670 100% 66
2804:8bac::/32 Valid Other IRR onlyRADB, TC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS273748: AS-AS273748. 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 (AS273748 isn't in the set, or no route object for AS273748 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 objectsAS273748 in itNot covered
AS-AS273748 In no IRR database read today.

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

  • ROA: maxLength2
  • ROA: none1
  • Route object: none2
  • Route object: RIR2
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:8bac::/33ROA 2804:8bac::/32 AS273748 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:8bac::/33.24 of 636
Route object: none2804:8bac::/33No route object for it. A route object for 2804:8bac::/32 with origin AS273748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273748 in the RIR database for the space.24 of 636
ROA: maxLength2804:8bac:8000::/33ROA 2804:8bac::/32 AS273748 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:8bac:8000::/33.24 of 636
Route object: none2804:8bac:8000::/33No route object for it. A route object for 2804:8bac::/32 with origin AS273748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273748 in the RIR database for the space.24 of 636
ROA: none38.19.59.0/24No ROA covers it. Add a ROA for AS273748, maxLength 24.670 of 673
Route object: RIR38.19.59.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:8bac::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS-AS273748PeeringDB names AS-AS273748; no IRR database read has it.

Route objects not announced

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