bgpreport

Network · data from 2026-11-12

AS267963 HAYAN TELECOM

Registry name: AS267963 - HAYAN TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267963, 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:55e4:6000::/35 Valid Nonecovered by 2804:55e4::/32 635 100% 68
2804:55e4::/33 Valid Nonecovered by 2804:55e4::/32 634 100% 67
2804:55e4:c000::/35 Valid Nonecovered by 2804:55e4::/32 625 98% 67
2804:55e4::/34 Valid Nonecovered by 2804:55e4::/32 331 52% 65
2804:55e4:4000::/34 Valid Nonecovered by 2804:55e4::/32 331 52% 65
45.166.150.0/23 Valid Other IRR onlyALTDB, RADB 672 100% 66
45.166.148.0/24 Valid Other IRR onlyALTDB 671 100% 67
45.166.149.0/24 Valid Other IRR onlyALTDB 666 99% 66
45.166.150.0/24 Valid Other IRR onlyALTDB, RADB 130 19% 45
45.166.151.0/24 Valid Other IRR onlyALTDB, RADB 130 19% 45

AS-SET

PeeringDB's irr_as_set for AS267963: AS-267963. 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 (AS267963 isn't in the set, or no route object for AS267963 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 objectsAS267963 in itNot covered
AS-267963 ALTDB 2217 Yes 0

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

  • Route object: none5
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2804:55e4:6000::/35No route object for it. A route object for 2804:55e4::/32 with origin AS267963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267963 in the RIR database for the space.635 of 636
Route object: none2804:55e4::/33No route object for it. A route object for 2804:55e4::/32 with origin AS267963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267963 in the RIR database for the space.634 of 636
Route object: none2804:55e4:c000::/35No route object for it. A route object for 2804:55e4::/32 with origin AS267963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267963 in the RIR database for the space.625 of 636
Route object: none2804:55e4::/34No route object for it. A route object for 2804:55e4::/32 with origin AS267963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267963 in the RIR database for the space.331 of 636
Route object: none2804:55e4:4000::/34No route object for it. A route object for 2804:55e4::/32 with origin AS267963 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267963 in the RIR database for the space.331 of 636
Route object: RIR45.166.150.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.166.148.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.166.149.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
Route object: RIR45.166.150.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.130 of 673
Route object: RIR45.166.151.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.130 of 673

Route objects not announced

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

45.166.148.0/22ALTDB, RADBNo ROA
45.166.148.0/23ALTDB, RADBValid
2804:55e4::/32ALTDB, RADBValid

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.