Catalog

JavaScript is used, and should be enabled to get full functionality.

Looking for catalogs ..

The VizieR service is now hosted by CDS domain (cds.unistra.fr). Please, modify your configuration for the new domain.

5 catalogs found

	J/ApJ/726/16	2990		{gamma}-ray loud blazars (Linford+, 2011) ReadMe+ftp 2011ApJ...726...16L Similar Catalogs
	J/ApJ/726/16/table1		^(c)LAT sources in VIPS (VLBA Imaging and Polarimetry Survey) (102 rows)
	J/ApJ/835/L38	4768		Fermi blazars with Doppler factors (Fan+, 2017) ReadMe+ftp 2017ApJ...835L..38F Similar Catalogs Interactive plot (part of Figure 1)
	J/ApJ/835/L38/blazars		^(c)Sample of Fermi blazars with Doppler factors and correlations for intrinsic values (table 1 and figures 1 and 2 data) (86 rows)
	J/ApJS/263/24	-1		The 4LAC-DR3 catalog (Ajello+, 2022) ReadMe+ftp 2022ApJS..263...24A Similar Catalogs
	J/ApJS/263/24/4lacdr3		^(c)4LAC-DR3 high (\|b\|>10deg) and low (\|b\|<10deg) Galactic latitude sources (original column names in green) (3814 rows)
	J/MNRAS/441/1899	801		Fermi bright blazars (Fuhrmann+, 2014) ReadMe+ftp 2014MNRAS.441.1899F Similar Catalogs
	J/MNRAS/441/1899/table2		^(c)List of selected sources included in the current analysis (69 rows)
	J/MNRAS/510/469	-1		Radio and {Gamma}-ray of MOJAVE-Fermi AGNs (Kramarenko+, 2022) ReadMe+ftp 2022MNRAS.510..469K Similar Catalogs timeSerie/pdf
	J/MNRAS/510/469/table1		^(c)Our sample of 331 bright blazars AGNs[timeSerie/pdf] (331 rows)
ALL
			^(c) indicates tables which contain celestial coordinates

The following problems were encountered in this VizieR run:

**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server

If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR3633175.err (2026-02-20T16:07:17)
-2
-kw.cat=74411899
-ref=VIZ699886b5377017

elapse time 1